Triple
T38159417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Pancras International high-speed services |
E952977
|
entity |
| Predicate | hasKeyOperator |
P193812
|
FINISHED |
| Object | Eurostar Group |
—
|
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: Eurostar Group | Statement: [St Pancras International high-speed services, hasKeyOperator, Eurostar Group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyOperator Context triple: [St Pancras International high-speed services, hasKeyOperator, Eurostar Group]
-
A.
hasKeyElement
Indicates that one entity contains or depends on another entity that serves as a primary or essential component.
-
B.
hasKeyFunction
Indicates that one entity serves as a primary or essential function or role for another entity.
-
C.
hasKeyFunctor
Indicates that one entity serves as the primary or key functor (main functional operator or mapping) associated with another entity.
-
D.
hasKeyArgumentType
Indicates that a key argument in a relation or event has a specific semantic or syntactic type.
-
E.
hasKeySupporter
Indicates that an entity has a primary or crucial supporter who significantly backs or advocates for it.
- 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
| PDg | Predicate description generation | batch_69fd553c01488190b9fda48b4a728f04 |
completed | May 8, 2026, 3:15 a.m. |
Created at: May 3, 2026, 4:21 p.m.