Triple
T7779604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EU–US Open Skies Agreement |
E221478
|
entity |
| Predicate | secondStageAgreementSignedOn |
P27237
|
FINISHED |
| Object | 2010-06-24 |
—
|
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: 2010-06-24 | Statement: [EU–US Open Skies Agreement, secondStageAgreementSignedOn, 2010-06-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondStageAgreementSignedOn Context triple: [EU–US Open Skies Agreement, secondStageAgreementSignedOn, 2010-06-24]
-
A.
agreementSignedAt
Indicates the specific time and/or place at which an agreement was formally signed.
-
B.
agreedAt
Indicates the time or point at which an agreement or consensus between parties was reached.
-
C.
dateSigned
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
D.
secondReachedDate
chosen
Indicates the date on which the second specified event, state, or condition is reached or occurs.
-
E.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
- 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_69ca83ebbef881909ac47f789145fef7 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
Created at: March 30, 2026, 4:19 p.m.