Triple
T34669227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GT Life |
E890332
|
entity |
| Predicate | B-SpecRole |
P67145
|
FINISHED |
| Object | player manages AI driver |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: player manages AI driver | Statement: [GT Life, B-SpecRole, player manages AI driver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: B-SpecRole Context triple: [GT Life, B-SpecRole, player manages AI driver]
-
A.
basisRole
Indicates that one role serves as the foundational or underlying role upon which another role or function is defined or derived.
-
B.
roleInSpecification
chosen
Indicates that an entity participates in a specification with a particular role or function within that specification.
-
C.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
-
D.
BIJACRole
Indicates a role-based relationship where an entity participates in or is assigned a specific role within a BIJAC context or structure.
-
E.
roleInBun
Indicates that an entity has a specific functional or contextual role within a particular bundle, grouping, or composite structure.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722fa31248190a1c9081ce8cfa37b |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.