Triple
T3730587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom in the Sky |
E79050
|
entity |
| Predicate | emphasizesFeature |
P7153
|
FINISHED |
| Object | Lesotho’s high elevation |
—
|
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: Lesotho’s high elevation | Statement: [Kingdom in the Sky, emphasizesFeature, Lesotho’s high elevation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasizesFeature Context triple: [Kingdom in the Sky, emphasizesFeature, Lesotho’s high elevation]
-
A.
hasEmphasis
Indicates that one element is given special stress, importance, or prominence relative to others.
-
B.
positionEmphasized
Indicates that a particular position, stance, or role is given special prominence or stress relative to others.
-
C.
keyFeature
chosen
Indicates that something is a primary, distinguishing, or most important feature of an entity.
-
D.
specialFeature
Indicates that an entity possesses a distinctive or noteworthy attribute, capability, or characteristic that sets it apart from others.
-
E.
strategyEmphasis
Indicates an entity’s primary focus or priority within a broader strategy or plan.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb1bb5408190990ea4dfbdab5c68 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.