Triple
T24352057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Automobilwerk Eisenach |
E613817
|
entity |
| Predicate | siteSuccessor |
P60563
|
FINISHED |
| Object | Opel Eisenach plant |
—
|
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: Opel Eisenach plant | Statement: [Automobilwerk Eisenach, siteSuccessor, Opel Eisenach plant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siteSuccessor Context triple: [Automobilwerk Eisenach, siteSuccessor, Opel Eisenach plant]
-
A.
successorSite
chosen
Indicates that one site directly follows and replaces another site in a sequence or evolution of sites.
-
B.
successorStateSite
Indicates that one site or state of a site directly follows another as its immediate successor in a sequence or process.
-
C.
serviceSuccessor
Indicates that one service continues, replaces, or follows another service in a sequence or lifecycle.
-
D.
successorBuildingOnSite
Indicates that one building directly replaces another on the same physical site or location.
-
E.
platformSuccessor
Indicates that one platform directly follows or replaces another in a sequence or evolution of platforms.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293467a508190937b9614870e243e |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:59 a.m.