Triple
T28026788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldwych tube station |
E708144
|
entity |
| Predicate | hasDisusedPlatform |
P71839
|
FINISHED |
| Object | one platform kept in near-original condition |
—
|
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: one platform kept in near-original condition | Statement: [Aldwych tube station, hasDisusedPlatform, one platform kept in near-original condition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisusedPlatform Context triple: [Aldwych tube station, hasDisusedPlatform, one platform kept in near-original condition]
-
A.
hasDisusedPlatforms
chosen
Indicates that an entity (such as a station or facility) possesses one or more platforms that are no longer in active use.
-
B.
hasPlatform2Usage
Indicates how a second platform is used or utilized in relation to another entity or system.
-
C.
hasPlatform1Usage
Indicates that an entity makes use of, or is utilized on, a specific primary platform.
-
D.
hadPlatforms
Indicates that something was equipped with or featured one or more platforms.
-
E.
coveredPlatform
Indicates that a platform is sheltered by a roof or overhead structure, providing cover from above.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 27, 2026, 8:13 p.m.