Triple
T24564502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matra MS80 |
E607744
|
entity |
| Predicate | wonConstructorsTitleFor |
P44378
|
FINISHED |
| Object | Matra |
—
|
NE NERFINISHED |
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: Matra | Statement: [Matra MS80, wonConstructorsTitleFor, Matra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wonConstructorsTitleFor Context triple: [Matra MS80, wonConstructorsTitleFor, Matra]
-
A.
resultedInConstructorsTitleFor
Indicates that one event, action, or condition caused or led to the assignment or creation of a specific constructor’s title for an entity.
-
B.
hasConstructorTitle
chosen
Indicates that an entity is associated with a specific title or designation held in its role as a constructor.
-
C.
constructorsTitleYear
Indicates that a constructor is associated with a specific title and the year in which that title was achieved or is relevant.
-
D.
builderTitle
Indicates the formal title or designation held by a person or entity in their role as a builder.
-
E.
namedForTitle
Indicates that one entity is named after or in honor of the title (such as a rank, honorific, or formal designation) associated with another entity.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f9d0f881909afc04537c32f76b |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.