Triple
T8970975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Development Goals |
E214264
|
entity |
| Predicate | wereAgreedIn |
P69481
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [International Development Goals, wereAgreedIn, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wereAgreedIn Context triple: [International Development Goals, wereAgreedIn, 1990s]
-
A.
agreement
Indicates that two or more parties mutually consent to and accept shared terms, conditions, or understandings.
-
B.
basedOnAgreementWith
Indicates that something exists, is done, or is determined on the basis of a prior agreement or accord between the involved parties.
-
C.
aimOfAgreement
Indicates the intended purpose or objective that an agreement is designed to achieve.
-
D.
involvedAgreement
Indicates that an entity participates in, is a party to, or is otherwise associated with a specific agreement or contract.
-
E.
agreedAt
chosen
Indicates the time or point at which an agreement or consensus between parties was reached.
- 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_69ca839dbf608190a2f5990477115d29 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67672c108190919ae6ca69b6291f |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:02 p.m.