Triple
T10591931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York and Long Branch Railroad |
E250011
|
entity |
| Predicate | servedStations |
P83367
|
FINISHED |
| Object | multiple shore resort communities |
—
|
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: multiple shore resort communities | Statement: [New York and Long Branch Railroad, servedStations, multiple shore resort communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedStations Context triple: [New York and Long Branch Railroad, servedStations, multiple shore resort communities]
-
A.
servesAsThroughStationFor
Indicates that a station functions as an intermediate (through) stop for a particular service, route, or journey rather than as its starting or ending point.
-
B.
numberOfStations
Indicates the total count of stations associated with or contained by a given entity.
-
C.
hasStations
chosen
Indicates that one entity possesses, contains, or is associated with one or more stations.
-
D.
operatedStation
Indicates that one entity managed, ran, or was responsible for the operation of a particular station.
-
E.
associatedStation
Indicates a relationship where one entity is linked or connected to a particular station as its relevant or related station.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5277c79808190acc872919eadd126 |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:40 p.m.