Triple
T9687296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castleton Corners |
E234442
|
entity |
| Predicate | servedByExpressBusRoute |
P39381
|
FINISHED |
| Object | SIM3 |
—
|
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: SIM3 | Statement: [Castleton Corners, servedByExpressBusRoute, SIM3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByExpressBusRoute Context triple: [Castleton Corners, servedByExpressBusRoute, SIM3]
-
A.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
B.
situatedOnTransportRoute
Indicates that one entity is located along, on, or directly adjacent to a specified transport route (such as a road, railway, or shipping lane).
-
C.
accessByBusFrom
Indicates that one location can be reached from another location using a bus as the mode of transportation.
-
D.
isPublicTransportRoute
Indicates that a given route is designated and operated as part of a public transportation system available for general use.
-
E.
hasBusServices
chosen
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9cd42cc081909abcf4c85592d950 |
completed | April 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:17 p.m.