Triple
T23640899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jersey City–Atlantic City |
E583886
|
entity |
| Predicate | usedByTrain |
P109578
|
FINISHED |
| Object | Blue Comet |
—
|
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: Blue Comet | Statement: [Jersey City–Atlantic City, usedByTrain, Blue Comet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByTrain Context triple: [Jersey City–Atlantic City, usedByTrain, Blue Comet]
-
A.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
B.
railwayUse
Indicates that something is used as, or functions in the capacity of, a railway or rail-based transportation facility.
-
C.
usedBetweenStations
Indicates that something (such as a service, route, or resource) is utilized in the context of travel or operation between two stations.
-
D.
usedByTransitSystem
chosen
Indicates that something is utilized or operated by a transit or public transportation system.
-
E.
trainTypeUsed
Indicates that a specific type or category of train is employed or operated in a given context or service.
- 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.