Triple
T4414565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashland/63rd station |
E94932
|
entity |
| Predicate | hasPlatformLocation |
P49408
|
FINISHED |
| Object | above 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: above street level | Statement: [Ashland/63rd station, hasPlatformLocation, above street level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlatformLocation Context triple: [Ashland/63rd station, hasPlatformLocation, above street level]
-
A.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
B.
platformLocation
chosen
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
C.
hasTargetPlatform
Indicates that something is intended to run on, be compatible with, or be deployed to a specified platform.
-
D.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
E.
supportsLocation
Indicates that one entity provides the necessary structure, foundation, or capacity to hold, host, or accommodate another entity at a particular place or position.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b354e940d48190b49cca6796d60de4 |
completed | March 13, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69b34f5d0c54819085c08533bb58030a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.