Triple
T1304455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OAS General Assembly resolutions |
E27841
|
entity |
| Predicate | canBeAdoptedAt |
P20295
|
FINISHED |
| Object | special sessions of the OAS General Assembly |
—
|
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: special sessions of the OAS General Assembly | Statement: [OAS General Assembly resolutions, canBeAdoptedAt, special sessions of the OAS General Assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeAdoptedAt Context triple: [OAS General Assembly resolutions, canBeAdoptedAt, special sessions of the OAS General Assembly]
-
A.
canAdopt
Indicates that one entity has the ability or permission to adopt another entity.
-
B.
adoptedAt
Indicates the time or date at which an adoption event took place.
-
C.
adoptedAfter
Indicates that one entity was adopted at a later time than another entity.
-
D.
officialAdoptionYear
Indicates the year in which something (such as a policy, standard, symbol, or practice) was formally adopted or officially put into use.
-
E.
adoptedAtEvent
chosen
Indicates that an entity formally became an adopter or was officially adopted during a specific event.
- 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c13393388190b784d6bd8c447dda |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4bee8544c8190874efd9bae9bccf9 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.