Triple
T34669226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GT Life |
E890332
|
entity |
| Predicate | A-SpecRole |
P90497
|
FINISHED |
| Object | player drives car directly |
—
|
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 drives car directly | Statement: [GT Life, A-SpecRole, player drives car directly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: A-SpecRole Context triple: [GT Life, A-SpecRole, player drives car directly]
-
A.
authorityRole
Indicates that one entity holds an official position or role that grants it authority or control over another entity or within a specific context.
-
B.
securityRole
Indicates that an entity holds a specific security-related role, permission level, or access profile within a system or context.
-
C.
antRole
chosen
Indicates that one entity has a specific role, function, or responsibility in relation to another entity.
-
D.
canonicalRole
Indicates that an entity holds a standard, primary, or officially recognized role within a particular context or system.
-
E.
admittedRole
Indicates that an entity has been formally accepted or recognized as holding a particular role or position.
- 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_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:05 a.m.