Triple
T26607674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senna |
E667826
|
entity |
| Predicate | portraysRivalry |
P178270
|
FINISHED |
| Object | Ayrton Senna–Alain Prost rivalry |
—
|
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: Ayrton Senna–Alain Prost rivalry | Statement: [Senna, portraysRivalry, Ayrton Senna–Alain Prost rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysRivalry Context triple: [Senna, portraysRivalry, Ayrton Senna–Alain Prost rivalry]
-
A.
rivalryCharacterizedBy
Indicates a relationship where a rivalry is defined or distinguished by a particular feature, quality, or circumstance.
-
B.
rivalPortrayedBy
Indicates that one entity is portrayed or depicted as the rival of another entity by a specific actor or creator.
-
C.
rivalryCharacterization
Indicates a relationship in which two entities are characterized as rivals, typically defined by ongoing competition, opposition, or conflict between them.
-
D.
involvesRivalryBetween
Indicates a relationship in which two or more entities are engaged in rivalry or competitive opposition with one another.
-
E.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
- 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 27, 2026, 2:15 a.m.