Triple
T35636268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Citroën C-Zero |
E1029728
|
entity |
| Predicate | sisterModel |
P170523
|
FINISHED |
| Object | Peugeot iOn |
—
|
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: Peugeot iOn | Statement: [Citroën C-Zero, sisterModel, Peugeot iOn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sisterModel Context triple: [Citroën C-Zero, sisterModel, Peugeot iOn]
-
A.
siblingModel
chosen
Indicates that two entities share at least one common parent, making them siblings in a familial or structural sense.
-
B.
sisterBody
Indicates that one celestial body is considered a counterpart or closely related “sibling” to another, typically due to similar characteristics, origin, or shared system.
-
C.
sisterModule
Indicates that two modules share a common parent or grouping, making them parallel or peer components within the same larger structure.
-
D.
sisterBase
Indicates that one entity is the sister of another, sharing at least one parent and being female relative to the other entity.
-
E.
sisterLine
Indicates that one entity is a sister of another within a family or genealogical relationship.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.