Triple
T34621139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Direct Rail Services |
E889004
|
entity |
| Predicate | operatesDepot |
P86339
|
FINISHED |
| Object | Kingmoor depot |
—
|
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: Kingmoor depot | Statement: [Direct Rail Services, operatesDepot, Kingmoor depot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesDepot Context triple: [Direct Rail Services, operatesDepot, Kingmoor depot]
-
A.
depot
Indicates that an entity serves as a storage or distribution center location for another entity, such as goods, vehicles, or resources.
-
B.
operatedDock
Indicates that an entity managed or controlled the functioning of a dock or docking facility.
-
C.
depotFor
chosen
Indicates that one entity serves as a storage or distribution center location dedicated to supporting or supplying another entity.
-
D.
operatesDepository
Indicates that one entity manages and runs the functions of a depository on behalf of another or within a given context.
-
E.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00c486d394819084fe93d5bb11ea1e |
completed | May 10, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_6a00c39d99d48190a94bfa057213499c |
completed | May 10, 2026, 5:42 p.m. |
Created at: May 1, 2026, 2:04 a.m.