Triple
T26208896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essex Thameside routes |
E655429
|
entity |
| Predicate | historicallyOperatedOn |
P181296
|
FINISHED |
| Object | London, Tilbury and Southend line |
—
|
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: London, Tilbury and Southend line | Statement: [Essex Thameside routes, historicallyOperatedOn, London, Tilbury and Southend line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyOperatedOn Context triple: [Essex Thameside routes, historicallyOperatedOn, London, Tilbury and Southend line]
-
A.
historicallyOperatedIn
Indicates that an entity carried out its activities or operations within a particular location or context during a past time period.
-
B.
historicallyOperatedAcross
Indicates that an entity has, at some point in the past, conducted operations or activities spanning multiple areas, domains, or regions.
-
C.
initiallyOperated
Indicates that an entity first began functioning, being used, or carrying out its intended operation at a specified initial time or under initial conditions.
-
D.
operatedSince
Indicates that an entity has been in operation continuously from a specified starting time or date.
-
E.
operatedDuring
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
| PDg | Predicate description generation | batch_69f7688cea58819098bdfd7c80df7634 |
completed | May 3, 2026, 3:23 p.m. |
Created at: April 26, 2026, 8:51 p.m.