Triple
T1412312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organisation of Islamic Cooperation |
E31830
|
entity |
| Predicate | charterAdopted |
P8747
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [Organisation of Islamic Cooperation, charterAdopted, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: charterAdopted Context triple: [Organisation of Islamic Cooperation, charterAdopted, 1972]
-
A.
constitutionAdopted
Indicates that a particular constitution has been formally accepted and put into effect by the relevant authority or polity.
-
B.
hasCharter
chosen
Indicates that an entity possesses, is governed by, or operates under a formal charter or foundational document.
-
C.
charterDate
Indicates the date on which an organization, institution, or entity was formally established or granted its charter.
-
D.
charterConfirmedBy
Indicates that an official charter has been formally approved or validated by a specified authority or entity.
-
E.
introducedLegalCharter
Indicates that an entity formally established or brought into effect a legal charter governing another entity or domain.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e3383c81909acb9c6c1c3b817a |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf048b648190ab77d9b45cb4855f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.