Triple
T27903770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN General Assembly Resolution 302 (IV) |
E705711
|
entity |
| Predicate | organCreated |
P26623
|
FINISHED |
| Object | UNRWA Advisory Commission |
—
|
NE NERFINISHED |
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: UNRWA Advisory Commission | Statement: [UN General Assembly Resolution 302 (IV), organCreated, UNRWA Advisory Commission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organCreated Context triple: [UN General Assembly Resolution 302 (IV), organCreated, UNRWA Advisory Commission]
-
A.
establishesOrgan
chosen
Indicates that an entity creates, founds, or sets up an organization or institutional body.
-
B.
órgãoCriado
Indicates that one entity is an organization or body that was created or established by another entity.
-
C.
organType
Indicates that one entity is classified as a specific type or category of organ in relation to another entity.
-
D.
organizationFounded
Indicates that an organization was established or created at a specific point in time, often by a particular founder or founding entity.
-
E.
organOrganization
Indicates that an organ is structurally or functionally part of, or associated with, a specific organization or organizational system.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 6:44 p.m.