Triple
T23720333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Two-thousanders of Canada |
E586122
|
entity |
| Predicate | hasUpperBoundExclusive |
P14327
|
FINISHED |
| Object | 3000 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: 3000 metres | Statement: [Two-thousanders of Canada, hasUpperBoundExclusive, 3000 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpperBoundExclusive Context triple: [Two-thousanders of Canada, hasUpperBoundExclusive, 3000 metres]
-
A.
includesUpperBound
Indicates that the specified range or interval contains and counts its upper limit value as part of the set.
-
B.
isUpperBoundFor
chosen
Indicates that one value is greater than or equal to every element in a given set or collection, serving as an upper limit for them.
-
C.
lessExclusiveThan
Indicates that one entity has a broader or more inclusive scope, membership, or applicability than another, which is more exclusive.
-
D.
isBoundedBelow
Indicates that every value in a set or function is greater than or equal to some fixed lower bound.
-
E.
hasLowerBoundaryDefinedBy
Indicates that one entity’s lower limit, edge, or boundary is specified or determined by 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.