Triple
T29033529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurostar e300 trainsets |
E737790
|
entity |
| Predicate | preRefurbishmentDesignation |
P165948
|
FINISHED |
| Object | Class 373 |
—
|
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: Class 373 | Statement: [Eurostar e300 trainsets, preRefurbishmentDesignation, Class 373]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preRefurbishmentDesignation Context triple: [Eurostar e300 trainsets, preRefurbishmentDesignation, Class 373]
-
A.
heritageDesignation
Indicates that an entity has been formally assigned a specific cultural, historical, or heritage protection status by an authority.
-
B.
heritageDesignationVia
Indicates that a heritage designation for an entity is conferred, recorded, or derived through a specific intermediary process, source, or mechanism.
-
C.
heritageDesignationSystem
Indicates the formal heritage classification or protection system under which an entity has been designated.
-
D.
heritageDesignationSubject
Indicates that a subject has been assigned a particular heritage designation or status.
-
E.
previousDesignationEstablished
Indicates that an earlier official designation or title for an entity was formally created or put into effect.
- F. None of above. chosen
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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6603acd608190b7e0ed75d26b6799 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65ad638ac8190a17bb987fce53279 |
completed | May 2, 2026, 8:13 p.m. |
Created at: April 28, 2026, 9:57 a.m.