Triple
T19819441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strand (Northern line) station |
E476146
|
entity |
| Predicate | laterAccessedBy |
P137448
|
FINISHED |
| Object | escalators |
—
|
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: escalators | Statement: [Strand (Northern line) station, laterAccessedBy, escalators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAccessedBy Context triple: [Strand (Northern line) station, laterAccessedBy, escalators]
-
A.
laterUsedBy
Indicates that something is subsequently utilized or employed by a specified entity at a later time.
-
B.
accessedThrough
Indicates that one entity is reached, used, or obtained by means of another entity that serves as an intermediary channel, tool, or pathway.
-
C.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
D.
formerAccess
Indicates that an entity previously had access to another entity or resource but no longer does.
-
E.
laterManagedBy
Indicates that an entity was, at a subsequent time, managed or overseen by 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654fe0ff8819084bad251b76eff77 |
completed | April 20, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:50 p.m.