Triple
T337035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human Development Index |
E6750
|
entity |
| Predicate | lowerValueIndicates |
P11409
|
FINISHED |
| Object | lower human development |
—
|
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: lower human development | Statement: [Human Development Index, lowerValueIndicates, lower human development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerValueIndicates Context triple: [Human Development Index, lowerValueIndicates, lower human development]
-
A.
lowestRank
Indicates that the subject has the least or worst rank in an ordered set compared to all other related entities.
-
B.
lowestPoint
Indicates that one entity is the point with the minimum vertical position or value relative to another entity or within a specified context.
-
C.
hasLower
Indicates that one entity is positioned at a lower level, rank, or value relative to another entity.
-
D.
belowLeague
Indicates that one entity is in a lower league, division, or competitive tier than another entity.
-
E.
lowerCourt
Indicates that one court holds a subordinate or inferior position in the judicial hierarchy relative to another court.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eac950388190829875a07d821ddf |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94f049881908f10bb6548a8bb2e |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea2af1388190b93235602ace679e |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.