Triple
T26475557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cedarhurst, New York |
E666021
|
entity |
| Predicate | railroadBranch |
P58624
|
FINISHED |
| Object | Far Rockaway Branch |
—
|
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: Far Rockaway Branch | Statement: [Cedarhurst, New York, railroadBranch, Far Rockaway Branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadBranch Context triple: [Cedarhurst, New York, railroadBranch, Far Rockaway Branch]
-
A.
railroadSubdivision
Indicates that one railroad line or territory is a designated subdivision (operational segment) of a larger railroad network.
-
B.
servedByRailBranch
chosen
Indicates that a location or facility is connected to and provided service by a specific railway branch line.
-
C.
railroadNetwork
Indicates a relationship where locations are connected as part of the same system of railway lines and infrastructure used for train transport.
-
D.
relatedRailroad
Indicates that there is an association or connection between an entity and a specific railroad, such as ownership, operation, service, or historical linkage.
-
E.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 12:23 a.m.