Triple
T18578984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rice Yard |
E454057
|
entity |
| Predicate | railroadTypeServed |
P21523
|
FINISHED |
| Object | freight |
—
|
LITERAL 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: freight | Statement: [Rice Yard, railroadTypeServed, freight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadTypeServed Context triple: [Rice Yard, railroadTypeServed, freight]
-
A.
railwayTypeServed
Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
-
B.
servedByRailroad
Indicates that a location or facility is provided with transportation or service by a railroad line or company.
-
C.
railServiceType
chosen
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
-
D.
isRailServiceOf
Indicates that a particular rail service operates for, belongs to, or is provided by a specified entity (such as a route, operator, or network).
-
E.
railInfrastructureServed
Indicates that a rail infrastructure facility or segment is served, accessed, or operated by a particular service, operator, or network.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543ce63188190b14a37c5ca9c2726 |
completed | April 19, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.