Triple
T28898983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darius |
E732901
|
entity |
| Predicate | laterEntriesFeature |
P195896
|
FINISHED |
| Object | 3D graphics |
—
|
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: 3D graphics | Statement: [Darius, laterEntriesFeature, 3D graphics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterEntriesFeature Context triple: [Darius, laterEntriesFeature, 3D graphics]
-
A.
laterEntriesFormat
Indicates that subsequent entries in a sequence or record follow a specified format or structural pattern.
-
B.
laterEntriesDateTo
Indicates that the related entries occur at a date later than (or up to a later cutoff date than) the referenced entry or date.
-
C.
laterFeature
Indicates that one feature, event, or element occurs or is introduced after another in time.
-
D.
laterShow
Indicates that one event, presentation, or showing occurs at a later time than another referenced event or showing.
-
E.
laterExtendedIn
Indicates that an existing entity (such as a work, version, or specification) was subsequently expanded, updated, or built upon by a later entity.
- F. None of above. chosen
Provenance (4 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69fdee75d1408190bba58a9cef200a54 |
completed | May 8, 2026, 2:08 p.m. |
Created at: April 28, 2026, 8:01 a.m.