Triple
T15816975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNH |
E383504
|
entity |
| Predicate | prioritizesOver |
P68004
|
FINISHED |
| Object | purely economic growth |
—
|
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: purely economic growth | Statement: [GNH, prioritizesOver, purely economic growth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prioritizesOver Context triple: [GNH, prioritizesOver, purely economic growth]
-
A.
prioritises
chosen
Indicates that one entity gives greater importance, preference, or precedence to another entity or task over alternatives.
-
B.
supportsPriority
Indicates that one entity provides functionality or capability for handling or honoring priority levels associated with another entity or operation.
-
C.
definesPriorOver
Indicates that one entity specifies or establishes a prior probability distribution over another entity.
-
D.
upgradePriorityBasedOn
Indicates that the priority level of something is increased or adjusted according to the status, attributes, or importance of another specified factor or entity.
-
E.
confersPrecedenceIn
Indicates that one entity is granted higher priority, rank, or standing over another within a specified context or domain.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a306a48190840adc49df2c26c5 |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.