Triple
T26488623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monument |
E664894
|
entity |
| Predicate | hasInterchangeWalkway |
P184576
|
FINISHED |
| Object | Bank station |
—
|
NE NERFINISHED |
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: Bank station | Statement: [Monument, hasInterchangeWalkway, Bank station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInterchangeWalkway Context triple: [Monument, hasInterchangeWalkway, Bank station]
-
A.
hasWalkwayWidth
Indicates the width measurement of a walkway in the relationship between a walkway and its specified dimension.
-
B.
hasWalkwayShape
Indicates that a walkway possesses a particular geometric or structural shape or configuration.
-
C.
hasWalkwayPosition
Indicates the spatial or relative position of an entity along or within a walkway.
-
D.
isScenicWalkway
Indicates that a path or route is designated as a walkway notable for its visually appealing or picturesque surroundings.
-
E.
hasEmergencyWalkway
Indicates that there is a designated emergency walkway available or present between the related entities.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: April 27, 2026, 12:32 a.m.