Triple
T23579746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lousios River |
E582164
|
entity |
| Predicate | hasGorgeLength |
P153257
|
FINISHED |
| Object | approximately 15 km |
—
|
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: approximately 15 km | Statement: [Lousios River, hasGorgeLength, approximately 15 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGorgeLength Context triple: [Lousios River, hasGorgeLength, approximately 15 km]
-
A.
hasNumberOfGorges
Indicates the relationship that specifies how many gorges are associated with a given entity.
-
B.
hasGorgeBelow
Indicates that one entity is situated above another entity such that a gorge lies directly below it.
-
C.
containsGorge
Indicates that one entity geographically includes or encompasses a gorge within its area or boundaries.
-
D.
gorgeWidth
Indicates the measured horizontal distance across a gorge from one side to the other.
-
E.
gorgeDepth
Indicates the measured vertical distance from a gorge’s rim down to its lowest point.
- F. None of above. chosen
Provenance (4 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1afd8e5ec81909fbdcf68bc14078e |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:39 p.m.