Triple
T292327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Atomic Energy Agency |
E6019
|
entity |
| Predicate | directorGeneralStart |
P10506
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [International Atomic Energy Agency, directorGeneralStart, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directorGeneralStart Context triple: [International Atomic Energy Agency, directorGeneralStart, 2019]
-
A.
executiveDirectorStart
Indicates the date or event when an individual begins serving as an executive director of an organization.
-
B.
formerDirector
Indicates that one entity previously held the position of director of the other entity but no longer does.
-
C.
secretaryGeneralStart
Indicates the date or point in time when an individual begins serving as secretary general of an organization or body.
-
D.
director
Indicates that one entity serves as the director (creative or managerial leader) of another entity, such as a film, organization, or project.
-
E.
manager
Indicates that one entity holds a supervisory or administrative role with authority and responsibility over another entity.
- F. None of above. chosen
Provenance (4 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea0dd1dc8190aecd5afdeb2fd74b |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e934b4408190b53a17f57a02df65 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea07e3bc8190bae593b3264de211 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.