Triple
T28826868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEAT Toledo |
E727930
|
entity |
| Predicate | successorInSegment |
P80604
|
FINISHED |
| Object | SEAT León sedan (in some markets) |
E194978
|
NE FINISHED |
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: SEAT León sedan (in some markets) | Statement: [SEAT Toledo, successorInSegment, SEAT León sedan (in some markets)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInSegment Context triple: [SEAT Toledo, successorInSegment, SEAT León sedan (in some markets)]
-
A.
successorInRegion
Indicates that one entity directly follows or replaces another within a specified region or jurisdiction.
-
B.
successorInPolicy
Indicates that one policy directly follows and replaces another in a sequence or hierarchy of policies.
-
C.
successorIndex
Indicates the position or identifier that directly follows a given index in an ordered sequence.
-
D.
hasSuccessorSegment
chosen
Indicates that one segment directly follows another segment in a sequence or ordered structure.
-
E.
successorOnRoute
Indicates that one entity directly follows another in sequence along a specified route.
- F. None of above.
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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24bba8f4388190b5b9e0d0f4ef0c63 |
completed | June 7, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: April 28, 2026, 6:36 a.m.