Triple
T253403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union of South American Nations |
E5385
|
entity |
| Predicate | treatySignedDate |
P439
|
FINISHED |
| Object | 23 May 2008 |
—
|
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: 23 May 2008 | Statement: [Union of South American Nations, treatySignedDate, 23 May 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatySignedDate Context triple: [Union of South American Nations, treatySignedDate, 23 May 2008]
-
A.
treatyDate
Indicates the calendar date on which a treaty is formally agreed upon, signed, or comes into effect between parties.
-
B.
dateOfConstitutionSigning
Indicates the date on which a constitution was formally signed or adopted.
-
C.
dateSigned
chosen
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
D.
peaceTreatySigned
Indicates that a formal peace treaty has been concluded and signed between previously opposing parties, establishing agreed terms to end or prevent conflict.
-
E.
ratifiedOn
Indicates the date or point in time at which an agreement, treaty, or formal decision was officially approved and made valid.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25d5331b48190b3797fece8e60e20 |
completed | Feb. 28, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69a25b678d6c81909780e1995c1ca691 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.