Triple
T17144191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imbros Gorge |
E416047
|
entity |
| Predicate | hasNarrowestWidth |
P126281
|
FINISHED |
| Object | approximately 1.5 meters |
—
|
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 1.5 meters | Statement: [Imbros Gorge, hasNarrowestWidth, approximately 1.5 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNarrowestWidth Context triple: [Imbros Gorge, hasNarrowestWidth, approximately 1.5 meters]
-
A.
hasApproximateMaximumWidth
Indicates that an entity’s maximum width is known only approximately, rather than as an exact value.
-
B.
hasWidth
Indicates that an entity possesses a specific measurement or extent along its width dimension.
-
C.
isNarrow
Indicates that something has a small width or limited breadth relative to a reference or context.
-
D.
hasMaximumBreadth
Indicates that an entity possesses the greatest breadth (widest extent) among a set of comparable entities or within a defined context.
-
E.
minimumWidth
Indicates that there is a specified smallest allowable or required width for something in the relationship.
- 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_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. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:36 a.m.