Triple
T18318329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prix de l'Arc de Triomphe |
E438804
|
entity |
| Predicate | firstRunningDate |
P19145
|
FINISHED |
| Object | 3 October 1920 |
—
|
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: 3 October 1920 | Statement: [Prix de l'Arc de Triomphe, firstRunningDate, 3 October 1920]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRunningDate Context triple: [Prix de l'Arc de Triomphe, firstRunningDate, 3 October 1920]
-
A.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
B.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
C.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
D.
firstRunningYear
chosen
Indicates the year in which something (such as an event, service, or operation) first began running or was initially active.
-
E.
firstShowDate
Indicates the date on which something (such as a show, event, or performance) is presented or broadcast for the very first time.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa342a881909afcd995405027af |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.