Triple
T17994531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OACPS |
E430465
|
entity |
| Predicate | adoptedRevisedGeorgetownAgreement |
P130046
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [OACPS, adoptedRevisedGeorgetownAgreement, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedRevisedGeorgetownAgreement Context triple: [OACPS, adoptedRevisedGeorgetownAgreement, 2019]
-
A.
GenevaActAdopted
Indicates that a formal act, agreement, or resolution associated with Geneva has been officially adopted or approved.
-
B.
adoptedWithTreaty
Indicates that something (such as a policy, measure, or standard) was formally adopted as part of, or through the ratification of, a specific treaty.
-
C.
reformedByTreaty
Indicates that an existing entity has been reorganized or restructured as a result of the terms of a formal treaty.
-
D.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
E.
confirmedTreaty
Indicates that an entity has formally approved, ratified, or validated a treaty, making the agreement officially recognized or in force.
- F. None of above. chosen
Provenance (4 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b3e29490819090ff221e7d7a9ddd |
completed | April 19, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:23 a.m.