Triple
T3977533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuranda Scenic Railway |
E85678
|
entity |
| Predicate | hasCarriages |
P5426
|
FINISHED |
| Object | heritage wooden carriages |
—
|
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: heritage wooden carriages | Statement: [Kuranda Scenic Railway, hasCarriages, heritage wooden carriages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCarriages Context triple: [Kuranda Scenic Railway, hasCarriages, heritage wooden carriages]
-
A.
carriageType
Indicates the specific kind or category of carriage associated with or used in relation to an entity.
-
B.
railwayCarriageUsedFor
Indicates that a railway carriage is employed or designated for a particular purpose, function, or type of use.
-
C.
usesRollingStock
chosen
Indicates that one entity employs or operates specific rolling stock (such as rail vehicles) in its activities or services.
-
D.
hasRackRailway
Indicates that one entity possesses or includes a rack railway system connecting locations or operating within its area.
-
E.
hasCarriagewayType
Indicates the specific structural or functional type of carriageway associated with a road segment (e.g., single, dual, or other carriageway configurations).
- 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_69aed93908348190a26c8aaf4fab3e86 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.