Triple
T3546524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bordeaux–Paris 1965 |
E75008
|
entity |
| Predicate | isMemorableFor |
P48006
|
FINISHED |
| Object | being dominated by Jacques Anquetil |
—
|
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: being dominated by Jacques Anquetil | Statement: [Bordeaux–Paris 1965, isMemorableFor, being dominated by Jacques Anquetil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMemorableFor Context triple: [Bordeaux–Paris 1965, isMemorableFor, being dominated by Jacques Anquetil]
-
A.
hasMemorableMoments
chosen
Indicates that something contains or is associated with particularly notable or unforgettable moments or events.
-
B.
famousForEvent
Indicates that an entity is widely known or recognized specifically because of a particular event.
-
C.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
D.
inscriptionFamousFor
Indicates that an inscription is widely recognized or notable specifically because of the referenced feature, event, content, or characteristic.
-
E.
commemorativeEvent
Indicates an event held specifically to honor, remember, or mark the significance of a person, group, or past occurrence.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfcf64488190af8452308734028c |
completed | March 8, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69adae15749881909b847c6ca73c934e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.