Triple
T12386527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latok IV |
E295878
|
entity |
| Predicate | routeCharacteristics |
P8860
|
FINISHED |
| Object | long sustained pitches |
—
|
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: long sustained pitches | Statement: [Latok IV, routeCharacteristics, long sustained pitches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeCharacteristics Context triple: [Latok IV, routeCharacteristics, long sustained pitches]
-
A.
routeNetworkCharacteristic
chosen
Indicates a relationship where a specific characteristic or property is attributed to a route within a network.
-
B.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
C.
transportationCharacteristic
Indicates a specific property, feature, or quality that characterizes a mode, means, or instance of transportation.
-
D.
routeDescription
Indicates a textual explanation or summary of the path, course, or itinerary taken between locations.
-
E.
roadTraverses
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fbd489c819098233a111442762e |
completed | April 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.