Triple
T23640605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Railroad of New Jersey |
E583877
|
entity |
| Predicate | connectedToRailroad |
P76977
|
FINISHED |
| Object | Reading Company |
—
|
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: Reading Company | Statement: [Central Railroad of New Jersey, connectedToRailroad, Reading Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToRailroad Context triple: [Central Railroad of New Jersey, connectedToRailroad, Reading Company]
-
A.
connectsToRailwayNetwork
Indicates that one entity is physically or functionally linked to a railway network, allowing access or transfer between them.
-
B.
servedByRailroad
Indicates that a location or facility is provided with transportation or service by a railroad line or company.
-
C.
relatedRailroad
chosen
Indicates that there is an association or connection between an entity and a specific railroad, such as ownership, operation, service, or historical linkage.
-
D.
enteredConrailOn
Indicates that an entity began employment with, or formally joined, Conrail on a specified date or at a specified time.
-
E.
hasRail
Indicates that something is equipped with, includes, or is connected to a rail or rail system.
- 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_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. |
Created at: April 17, 2026, 6:48 p.m.