Triple
T1434808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Liverpool Street |
E30536
|
entity |
| Predicate | hasMainLinePlatformCount |
P843
|
FINISHED |
| Object | 18 |
—
|
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: 18 | Statement: [London Liverpool Street, hasMainLinePlatformCount, 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainLinePlatformCount Context triple: [London Liverpool Street, hasMainLinePlatformCount, 18]
-
A.
hasNumberOfPlatforms
chosen
Indicates the relationship that specifies how many platforms are associated with a given entity.
-
B.
hasPrimaryPlatform
Indicates that one entity is designated as the main or principal platform associated with another entity.
-
C.
hasMainTrunkLine
Indicates that an entity is connected to or served by a primary or central trunk line within a network or system.
-
D.
hasTerminatingPlatforms
Indicates that the subject location or facility includes platforms where rail or transit services begin or end their routes, rather than passing through.
-
E.
hasLanes
Indicates that an entity, such as a road or pathway, is divided into one or more distinct lanes for traffic or movement.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5ff8dbc81909eafcfc9f2260a22 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c478f65481909ee716791c663491 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.