Triple
T24577309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acropolis Rally |
E608148
|
entity |
| Predicate | notableManufacturerSuccess |
P83536
|
FINISHED |
| Object | Lancia |
—
|
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: Lancia | Statement: [Acropolis Rally, notableManufacturerSuccess, Lancia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableManufacturerSuccess Context triple: [Acropolis Rally, notableManufacturerSuccess, Lancia]
-
A.
notableManufacturer
Indicates that an entity is a well-known or prominent producer or maker of another entity.
-
B.
successorManufacturer
Indicates that one manufacturer has taken over, replaced, or continued the role or operations of another manufacturer as its successor.
-
C.
winningManufacturer
Indicates that a manufacturer is the one that won a particular competition, contract, award, or selection process.
-
D.
notableEnterprise
Indicates that an entity is a business or commercial organization recognized for its significance, prominence, or impact.
-
E.
hasNotableSuccessIn
chosen
Indicates that an entity has achieved significant or widely recognized success in a particular field, activity, or domain.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a97be2ac8190aecf5e54a37e266a |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.