Triple
T17144204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imbros Gorge |
E416047
|
entity |
| Predicate | trailDuration |
P53572
|
FINISHED |
| Object | approximately 2 to 3 hours |
—
|
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 2 to 3 hours | Statement: [Imbros Gorge, trailDuration, approximately 2 to 3 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailDuration Context triple: [Imbros Gorge, trailDuration, approximately 2 to 3 hours]
-
A.
hasTrailDuration
chosen
Indicates that an entity (such as a trail or route) is associated with a specific amount of time required to traverse or complete it.
-
B.
trailDistanceContext
Indicates the contextual distance or separation between entities along a trail, path, or route.
-
C.
trailLengthApprox
Indicates an approximate measurement of the total length of a trail.
-
D.
trailLengthCategory
Indicates the classification of a trail based on its total length (e.g., short, medium, long).
-
E.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2d8ca8c81909bba0cd6d60a4776 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.