Triple
T30731351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICAN Convention |
E782430
|
entity |
| Predicate | organizationTypeCreated |
P3580
|
FINISHED |
| Object | intergovernmental technical body |
—
|
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: intergovernmental technical body | Statement: [ICAN Convention, organizationTypeCreated, intergovernmental technical body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizationTypeCreated Context triple: [ICAN Convention, organizationTypeCreated, intergovernmental technical body]
-
A.
organizationType
chosen
Indicates the specific category or classification of an organization in terms of its nature, structure, or primary function.
-
B.
agencyTypeCreated
Indicates that a specific type or category of agency has been created or established.
-
C.
creatorOrganizationType
Indicates the type or category of organization that created or is responsible for the entity.
-
D.
organizationTypeLed
Indicates that an entity holds a leadership role over an organization of a specified type.
-
E.
createdAgency
Indicates that one entity brought an agency into existence, establishing it as a new organizational or institutional body.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 29, 2026, 8:37 p.m.