Triple
T28107567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferrari F2005 |
E710402
|
entity |
| Predicate | competitiveRivals |
P30601
|
FINISHED |
| Object | Renault R25 |
—
|
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: Renault R25 | Statement: [Ferrari F2005, competitiveRivals, Renault R25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitiveRivals Context triple: [Ferrari F2005, competitiveRivals, Renault R25]
-
A.
competitiveDiscipline
Indicates a relationship where an entity participates in or is associated with a structured, rule-based activity or field in which individuals or groups compete against each other.
-
B.
competitionFrom
chosen
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
C.
competitiveContext
Indicates a situation in which entities are engaged in or influenced by competition with one another.
-
D.
competition
Indicates a relationship where two or more entities strive against each other to achieve a superior outcome, advantage, or reward.
-
E.
isCompetitive
Indicates that one entity engages in rivalry or competition with another, typically striving to outperform or win against it.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 9:09 p.m.