Triple
T10351611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compagnie de Fives-Lille |
E243893
|
entity |
| Predicate | structureTypeBuilt |
P93817
|
FINISHED |
| Object | railway stations |
—
|
LITERAL 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: railway stations | Statement: [Compagnie de Fives-Lille, structureTypeBuilt, railway stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structureTypeBuilt Context triple: [Compagnie de Fives-Lille, structureTypeBuilt, railway stations]
-
A.
builtStructureFor
Indicates that one entity constructed or assembled a structure specifically intended for the use, benefit, or purpose of another entity.
-
B.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
C.
originalStructureType
Indicates the type or category of the structure that an entity originally had before any changes or transformations.
-
D.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
E.
definesStructure
Indicates that one entity specifies or determines the organizational form, composition, or arrangement of another entity.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9489f9481908fc1c818e81c1cc2 |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 11:57 a.m.