Triple
T18924938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Leader |
E462949
|
entity |
| Predicate | isPrincipleOf |
P78892
|
FINISHED |
| Object | UN development system reform |
—
|
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: UN development system reform | Statement: [One Leader, isPrincipleOf, UN development system reform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrincipleOf Context triple: [One Leader, isPrincipleOf, UN development system reform]
-
A.
usesPrinciple
Indicates that one entity applies, relies on, or is based upon a particular principle in its functioning, reasoning, or design.
-
B.
recognizesPrinciple
Indicates that an entity acknowledges the validity, authority, or applicability of a particular principle.
-
C.
implementsPrinciple
Indicates that an entity applies, follows, or puts into practice a specified principle in its design, behavior, or operation.
-
D.
includePrinciple
Indicates that one entity incorporates, embodies, or is based on a particular principle defined by another entity.
-
E.
representsPrinciple
chosen
Indicates that one entity serves as a fundamental rule, law, or guiding concept that underlies, explains, or governs another entity.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9b77c188190b2274ef45d538508 |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:59 a.m.