Triple
T161754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston’s North Station (via Fitchburg Line) |
E3301
|
entity |
| Predicate | hasConnectionType |
P1374
|
FINISHED |
| Object | intermodal connection with rapid transit |
—
|
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: intermodal connection with rapid transit | Statement: [Boston’s North Station (via Fitchburg Line), hasConnectionType, intermodal connection with rapid transit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectionType Context triple: [Boston’s North Station (via Fitchburg Line), hasConnectionType, intermodal connection with rapid transit]
-
A.
connectorType
chosen
Indicates the specific kind or category of connection interface that links two entities.
-
B.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
C.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
D.
hasOperationType
Indicates the specific kind or category of operation associated with an entity or process.
-
E.
hasCapacityType
Indicates that an entity possesses a specific kind or classification of capacity or capability.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2585877648190a2ec320182a69343 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256623704819089d9eeefe05858ce |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.