Triple
T1968097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human Development Report |
E42734
|
entity |
| Predicate | goesBeyond |
P20249
|
FINISHED |
| Object | income-based measures of 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: income-based measures of development | Statement: [Human Development Report, goesBeyond, income-based measures of development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goesBeyond Context triple: [Human Development Report, goesBeyond, income-based measures of development]
-
A.
beyond
chosen
Indicates that one entity is located or extends farther than, or outside the limits or scope of, another reference point or boundary.
-
B.
liesBeyond
Indicates that one entity is located at a greater distance or outside the boundary of another reference point, region, or limit.
-
C.
reaches
Indicates that one entity extends or moves until it makes contact with, attains, or arrives at another entity or point.
-
D.
goesTo
Indicates that one entity moves or travels from its current location to another specified location or entity.
-
E.
over
Indicates that one entity is positioned higher than and extending across or above another entity, often covering or spanning it.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3cf15048190a51f73ed85e1b958 |
completed | March 7, 2026, 5:12 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.