Triple
T23720334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Two-thousanders of Canada |
E586122
|
entity |
| Predicate | hasLowerBoundInclusive |
P7353
|
FINISHED |
| Object | 2000 metres |
—
|
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: 2000 metres | Statement: [Two-thousanders of Canada, hasLowerBoundInclusive, 2000 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowerBoundInclusive Context triple: [Two-thousanders of Canada, hasLowerBoundInclusive, 2000 metres]
-
A.
hasLowerBoundaryDefinedBy
Indicates that one entity’s lower limit, edge, or boundary is specified or determined by another entity.
-
B.
isBoundedBelow
Indicates that every value in a set or function is greater than or equal to some fixed lower bound.
-
C.
includesUpperBound
Indicates that the specified range or interval contains and counts its upper limit value as part of the set.
-
D.
hasMinimumValue
chosen
Indicates that an entity possesses a value that is the lowest permissible or observed within a specified set, range, or context.
-
E.
hasLower
Indicates that one entity is positioned at a lower level, rank, or value relative to another entity.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b910759c8190be189db3e86d7258 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7 p.m.