Triple
T1346337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uruguay |
E28578
|
entity |
| Predicate | HDIRanking |
P1944
|
FINISHED |
| Object | very high 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: very high human development | Statement: [Uruguay, HDIRanking, very high human development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HDIRanking Context triple: [Uruguay, HDIRanking, very high human development]
-
A.
globalRanking
Indicates the position or status of an entity relative to all comparable entities worldwide according to some ranking criteria.
-
B.
depthRank
Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
-
C.
rankedAs
chosen
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
-
D.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
E.
SSRank
Indicates a ranking relationship that orders entities based on their social status, standing, or relative importance within a specified 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c23e84188190b0395c57dd45b62a |
completed | March 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.