Triple
T27520351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Summit for Social Development |
E694690
|
entity |
| Predicate | numberOfCommitments |
P198355
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [World Summit for Social Development, numberOfCommitments, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfCommitments Context triple: [World Summit for Social Development, numberOfCommitments, 10]
-
A.
numberOfCommissions
Indicates the quantity of commissions associated with or assigned to a given entity.
-
B.
guaranteeCommitments
Indicates a relationship where one party formally assures that specific obligations or promises made to another party will be fulfilled or upheld.
-
C.
fundingCommitment
Indicates a promise or obligation by one party to provide a specified amount or type of funding to another party or project.
-
D.
numberOfGrants
Indicates the total count of grants associated with a given entity or context.
-
E.
coreCommitment
Indicates a fundamental, central obligation or promise that defines the primary responsibility or dedication within a relationship or agreement.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69fedfd850ec81909b55f90dc850167e |
completed | May 9, 2026, 7:18 a.m. |
Created at: April 27, 2026, 1:20 p.m.