Triple
T37404964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bus stand B |
E929100
|
entity |
| Predicate | inStationType |
P27765
|
FINISHED |
| Object | bus station |
—
|
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: bus station | Statement: [Bus stand B, inStationType, bus station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inStationType Context triple: [Bus stand B, inStationType, bus station]
-
A.
stationType
chosen
Indicates the specific category or classification of a station based on its function, services, or operational characteristics.
-
B.
isStationOf
Indicates that a given location functions as a station (e.g., transport or service hub) associated with or serving a particular system, line, route, or organization.
-
C.
servesStationType
Indicates that an entity provides service to, or operates in connection with, a particular type or category of station.
-
D.
hadStationType
Indicates that an entity (such as a station) possessed or was classified by a particular type or category of station.
-
E.
hasStationTypeAt
Indicates that a specific type of station is present or assigned at a particular location or point.
- 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.