Triple
T36105932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GATT GPA |
E1044354
|
entity |
| Predicate | revisedAgreementEnteredIntoForce |
P11446
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [GATT GPA, revisedAgreementEnteredIntoForce, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revisedAgreementEnteredIntoForce Context triple: [GATT GPA, revisedAgreementEnteredIntoForce, 2014]
-
A.
treatyEnteredIntoForce
chosen
Indicates that a treaty has become legally binding and operative for the parties involved after meeting its specified conditions for entry into force.
-
B.
agreedAt
Indicates the time or point at which an agreement or consensus between parties was reached.
-
C.
agreementSignedAt
Indicates the specific time and/or place at which an agreement was formally signed.
-
D.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
-
E.
internationalAgreementSignedAt
Indicates that an international agreement was formally signed at a specific location.
- 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:08 p.m.