Triple
T26672576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mala Rijeka Viaduct |
E672372
|
entity |
| Predicate | designedToCross |
P135385
|
FINISHED |
| Object | deep canyon |
—
|
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: deep canyon | Statement: [Mala Rijeka Viaduct, designedToCross, deep canyon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToCross Context triple: [Mala Rijeka Viaduct, designedToCross, deep canyon]
-
A.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
B.
crossingType
Indicates the specific kind or category of crossing (e.g., how or where one thing passes over, through, or across another).
-
C.
crossedBy
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
-
D.
crossesTo
Indicates that one entity moves or extends from one side or area to another, passing over or through some boundary or intervening space.
-
E.
crossesTerrain
chosen
Indicates that an entity moves or extends from one side of a specified terrain feature to the other, traversing it as part of its path or location.
- 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 3:13 a.m.