Triple
T25467293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alain Prost |
E638209
|
entity |
| Predicate | racedWithEngineSupplier |
P17328
|
FINISHED |
| Object | TAG-Porsche |
—
|
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: TAG-Porsche | Statement: [Alain Prost, racedWithEngineSupplier, TAG-Porsche]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racedWithEngineSupplier Context triple: [Alain Prost, racedWithEngineSupplier, TAG-Porsche]
-
A.
racedForManufacturer
Indicates that an individual competed in races as a driver representing a particular manufacturer.
-
B.
engineSupplier
chosen
Indicates a relationship where one entity supplies or provides engines to another entity.
-
C.
racedAs
Indicates that one entity participated in a race or competition under the identity, name, or classification of another entity.
-
D.
initiallyRacedWith
Indicates that two entities participated in the same race or competitive event at the beginning of a relevant period or career.
-
E.
raceComponent
Indicates that one entity is a constituent part, segment, or stage within a larger race or racing event involving 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f74e449c8190afaa3c05496ed598 |
completed | May 2, 2026, 1:08 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:15 p.m.