Triple
T21282757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbican station |
E524568
|
entity |
| Predicate | hasRunningLines |
P4876
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Barbican station, hasRunningLines, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRunningLines Context triple: [Barbican station, hasRunningLines, 3]
-
A.
hasFastLines
Indicates that the subject possesses or is associated with lines that operate or move at a high speed.
-
B.
hasNumberOfLines
chosen
Indicates the relationship that specifies how many lines are associated with a given entity.
-
C.
hasLineUnderConstruction
Indicates that a line (such as a route, track, or service line) associated with an entity is currently in the process of being built, upgraded, or otherwise under construction.
-
D.
hasDeepLevelLines
Indicates that one entity possesses or exhibits lines that extend to or occur at a deep level within a given structure or context.
-
E.
hasDeFactoLine
Indicates that there exists an unofficial or non-legally recognized boundary or demarcation line functioning in practice between the related entities.
- 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_69e0b5171f6c8190a5d57201ede73811 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736d3dfbc819081bd876d95c7c480 |
completed | April 21, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:03 p.m.