Triple
T33998720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R22 |
E871749
|
entity |
| Predicate | isInRailwaySector |
P68241
|
FINISHED |
| Object | passenger transport |
—
|
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: passenger transport | Statement: [R22, isInRailwaySector, passenger transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInRailwaySector Context triple: [R22, isInRailwaySector, passenger transport]
-
A.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
-
B.
railwayNetworkSector
chosen
Indicates a relationship where something is classified as, or associated with, a specific sector or segment of a railway network.
-
C.
isOnRailway
Indicates that one entity is positioned on, aligned with, or traveling along a railway track or railway system in relation to another entity.
-
D.
railwaySectorOrigin
Indicates the place or source from which a railway sector, line, or system originates or begins.
-
E.
hasRailwayZone
Indicates that a location or railway entity falls under the jurisdiction or coverage area of a specific railway zone.
- 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:50 a.m.