Triple
T23640594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Railroad of New Jersey |
E583877
|
entity |
| Predicate | usedFerryServiceTo |
P152996
|
FINISHED |
| Object | Manhattan |
—
|
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: Manhattan | Statement: [Central Railroad of New Jersey, usedFerryServiceTo, Manhattan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedFerryServiceTo Context triple: [Central Railroad of New Jersey, usedFerryServiceTo, Manhattan]
-
A.
hasFerryService
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
-
B.
hasFerryType
Indicates that an entity (such as a ferry route or service) is associated with a specific type or category of ferry.
-
C.
hasFerryComponent
Indicates that something includes or is associated with a ferry-related part, feature, or segment within its structure or operation.
-
D.
ferryServiceEnded
Indicates that a previously operating ferry service between locations has been discontinued or terminated.
-
E.
ferryServiceName
Indicates the specific name assigned to a ferry service operating between locations.
- F. None of above. chosen
Provenance (4 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b2808d888190a2198f5efd25f2df |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f1233300bc8190ac1639bdca1d7d99 |
completed | April 28, 2026, 9:14 p.m. |
Created at: April 17, 2026, 6:48 p.m.