Triple
T1834654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Werburgh's Road tram stop |
E41037
|
entity |
| Predicate | formerTerminusUntil |
P28772
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [St Werburgh's Road tram stop, formerTerminusUntil, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerTerminusUntil Context triple: [St Werburgh's Road tram stop, formerTerminusUntil, 2013]
-
A.
formerTerminusFor
chosen
Indicates that a location once served as the endpoint or final stop of a route, line, or service, but no longer holds that status.
-
B.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
C.
governsUntil
Indicates that one entity exercises governing authority or control over another entity up to, but not beyond, a specified time or condition.
-
D.
basedInUntil
Indicates that an entity was based or located in a particular place up to a specified end time or date, after which this association ceased.
-
E.
existedUntil
Indicates that an entity continued to exist up to, but not necessarily beyond, a specified time or event.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafd88ebc81908208394746351fe6 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.