Triple
T25322816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACHPR |
E634929
|
entity |
| Predicate | foundingInstrumentEnteredIntoForce |
P39113
|
FINISHED |
| Object | 1986 |
—
|
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: 1986 | Statement: [ACHPR, foundingInstrumentEnteredIntoForce, 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingInstrumentEnteredIntoForce Context triple: [ACHPR, foundingInstrumentEnteredIntoForce, 1986]
-
A.
charterEnteredIntoForce
Indicates that a charter has become legally effective and binding as of a specific point in time.
-
B.
foundingInstrumentAdopted
Indicates that a foundational legal or organizational instrument (such as a charter, constitution, or treaty) has been formally adopted or brought into effect.
-
C.
treatyEnteredIntoForce
Indicates that a treaty has become legally binding and operative for the parties involved after meeting its specified conditions for entry into force.
-
D.
yearEnteredIntoForce
chosen
Indicates the year in which an agreement, law, treaty, or similar instrument officially became legally effective or operational.
-
E.
foundingTreatySignedAt
Indicates that the founding treaty establishing an entity 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 21, 2026, 1:29 p.m.