Triple
T2876987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerch Strait |
E56900
|
entity |
| Predicate | hasWidthMin |
P12977
|
FINISHED |
| Object | approximately 3.1 kilometers |
—
|
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 3.1 kilometers | Statement: [Kerch Strait, hasWidthMin, approximately 3.1 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWidthMin Context triple: [Kerch Strait, hasWidthMin, approximately 3.1 kilometers]
-
A.
hasWidth
Indicates that an entity possesses a specific measurement or extent along its width dimension.
-
B.
hasMinimumSize
Indicates that an entity meets or exceeds a specified minimum size threshold.
-
C.
minimumWidth
chosen
Indicates that there is a specified smallest allowable or required width for something in the relationship.
-
D.
hasApproximateMaximumWidth
Indicates that an entity’s maximum width is known only approximately, rather than as an exact value.
-
E.
hasMinimumValue
Indicates that an entity possesses a value that is the lowest permissible or observed within a specified set, range, or context.
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe007329c8190b0bc1851c7307124 |
completed | March 7, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.