Triple
T29641927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Union Treaty |
E755883
|
entity |
| Predicate | scheduledSigningDate |
P439
|
FINISHED |
| Object | 1991-08-20 |
—
|
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: 1991-08-20 | Statement: [New Union Treaty, scheduledSigningDate, 1991-08-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scheduledSigningDate Context triple: [New Union Treaty, scheduledSigningDate, 1991-08-20]
-
A.
dateSigned
chosen
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
B.
signaturesTargetDate
Indicates the date by which the required signatures are expected to be obtained or completed.
-
C.
scheduledAs
Indicates that one entity is assigned or arranged to occur or function in the role, time, or capacity specified by another entity within a schedule.
-
D.
signedOnCalendar
Indicates that an entity has placed its signature or mark on a specific calendar date or entry.
-
E.
agreementSignedAt
Indicates the specific time and/or place at which an agreement was formally signed.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f66ed0653c819085adda918bd12f83 |
completed | May 2, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:47 p.m.