Triple
T34571902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | former Central Railroad of New Jersey main line |
E887646
|
entity |
| Predicate | hadTerminal |
P53208
|
FINISHED |
| Object | Communipaw Terminal |
E583881
|
NE 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: Communipaw Terminal | Statement: [former Central Railroad of New Jersey main line, hadTerminal, Communipaw Terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadTerminal Context triple: [former Central Railroad of New Jersey main line, hadTerminal, Communipaw Terminal]
-
A.
usedTerminal
Indicates that an entity made use of or interacted with a particular terminal or endpoint device.
-
B.
hasTerminalFacility
chosen
Indicates that an entity possesses or includes a terminal facility used as an endpoint for transport, communication, or related operations.
-
C.
hasIntegratedTerminal
Indicates that one entity includes or supports a built-in terminal interface as part of its functionality.
-
D.
hasTerminalService
Indicates that one entity provides or is associated with a terminal-related service (such as an endpoint, station, or final service point) for another entity.
-
E.
hadSystem
Indicates that an entity possessed, used, or was associated with a particular system.
- F. None of above.
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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72094e2b48190b7e1d98623ceef0e |
completed | May 3, 2026, 10:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37362f88d08190a78b2ea424a0e221 |
completed | June 21, 2026, 12:54 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:03 a.m.