Triple
T30276096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trem do Corcovado |
E769947
|
entity |
| Predicate | usesRailwayType |
P63327
|
FINISHED |
| Object | rack railway |
—
|
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: rack railway | Statement: [Trem do Corcovado, usesRailwayType, rack railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRailwayType Context triple: [Trem do Corcovado, usesRailwayType, rack railway]
-
A.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
B.
hasRailwayInfrastructureType
chosen
Indicates that an entity possesses or is associated with a specific type or category of railway infrastructure.
-
C.
hasRailMode
Indicates that an entity is associated with or supports transportation via rail-based modes (such as trains, trams, or subways).
-
D.
railwayUse
Indicates that something is used as, or functions in the capacity of, a railway or rail-based transportation facility.
-
E.
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.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 7:44 p.m.