Triple
T23760610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S (Shuttle) train |
E587237
|
entity |
| Predicate | connectsMajorStations |
P111188
|
FINISHED |
| Object | Times Square–42nd Street |
—
|
NE NERFINISHED |
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: Times Square–42nd Street | Statement: [S (Shuttle) train, connectsMajorStations, Times Square–42nd Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsMajorStations Context triple: [S (Shuttle) train, connectsMajorStations, Times Square–42nd Street]
-
A.
connectsMajorHub
chosen
Indicates that one entity serves as a link or route between major hubs or primary nodes in a network.
-
B.
otherMainStations
Indicates that an entity is associated with additional primary stations beyond its main or primary station.
-
C.
hasMajorRailLinksTo
Indicates that there are significant railway connections or routes between two locations.
-
D.
connectsMajorCity
Indicates that one entity serves as a link or route providing direct connection to a major city.
-
E.
otherMajorTerminal
Indicates that an entity is associated with a different primary terminal or endpoint than the one currently referenced or considered.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdb289508190a4a1049762102794 |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:14 p.m.