Triple
T25359273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davisville |
E635912
|
entity |
| Predicate | railwayStopOn |
P72542
|
FINISHED |
| Object | California Pacific Railroad |
—
|
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: California Pacific Railroad | Statement: [Davisville, railwayStopOn, California Pacific Railroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayStopOn Context triple: [Davisville, railwayStopOn, California Pacific Railroad]
-
A.
hasRailwayStationOn
chosen
Indicates that a railway station is located on or serves a particular railway line, route, or network segment.
-
B.
railTerminus
Indicates that a railway line or service ends at a particular station or location, which serves as its final terminus.
-
C.
railTerminusFor
Indicates that one location serves as the final or terminal rail station or endpoint for a specified rail line or service.
-
D.
hasRailwayStationRole
Indicates that an entity holds or is assigned a specific functional role or capacity within the operation or management of a railway station.
-
E.
railwayStationFor
Indicates a relationship where a railway station serves, is designated for, or primarily associated with a particular place, line, 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f49e0441108190be510b7bf3a22cea |
completed | May 1, 2026, 12:35 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 1:36 p.m.