Triple
T36105931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GATT GPA |
E1044354
|
entity |
| Predicate | revisedAgreementAdopted |
P130046
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [GATT GPA, revisedAgreementAdopted, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revisedAgreementAdopted Context triple: [GATT GPA, revisedAgreementAdopted, 2012]
-
A.
agreedOn
Indicates that two or more parties have reached a mutual agreement or consensus regarding a specific matter, decision, or proposal.
-
B.
adoptedDocument
Indicates that an authoritative body has formally approved and accepted a specific document as official or binding.
-
C.
adoptedRevisedGeorgetownAgreement
chosen
Indicates that an entity has formally accepted and put into effect the terms of the Revised Georgetown Agreement.
-
D.
adoptedPursuantTo
Indicates that something (such as a measure, policy, or decision) was formally adopted in accordance with, and on the basis of, a specific legal authority, procedure, or instrument.
-
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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.