Triple
T17465451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saluki |
E425263
|
entity |
| Predicate | railroadLineCategory |
P14639
|
FINISHED |
| Object | intercity passenger rail line |
—
|
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: intercity passenger rail line | Statement: [Saluki, railroadLineCategory, intercity passenger rail line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadLineCategory Context triple: [Saluki, railroadLineCategory, intercity passenger rail line]
-
A.
railwayLineType
chosen
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
-
B.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
C.
railCorridorType
Indicates the specific classification or type of a rail corridor associated with the subject (e.g., mainline, branch line, high-speed, freight, etc.).
-
D.
railwayLineRole
Indicates the specific functional role or purpose that a railway line serves within a rail network or transportation system.
-
E.
railroadClass
Indicates the classification or category of a railroad according to an established system (e.g., by size, revenue, or regulatory status).
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451a6c2e08190bca9de56ee2f5136 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.