Triple
T3396315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterfront station |
E71536
|
entity |
| Predicate | platformLocation |
P49408
|
FINISHED |
| Object | below street level |
—
|
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: below street level | Statement: [Waterfront station, platformLocation, below street level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformLocation Context triple: [Waterfront station, platformLocation, below street level]
-
A.
portalLocation
Indicates that a portal is situated at or associated with a specific location.
-
B.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
-
C.
locationOfFacility
Indicates that a facility is situated at or associated with a specific geographic location.
-
D.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
E.
plateLocation
Indicates the spatial position or placement of a plate relative to a reference location or object.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb856158c81908dd7d3f1f8d6af74 |
completed | March 8, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb2e426b88190b82d9830149b142e |
completed | March 8, 2026, 5:33 p.m. |
Created at: March 8, 2026, 3:14 p.m.