Triple
T6781257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 Presidential Inaugural Committee |
E155686
|
entity |
| Predicate | organizedForOffice |
P72789
|
FINISHED |
| Object | President of the United States |
—
|
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: President of the United States | Statement: [2013 Presidential Inaugural Committee, organizedForOffice, President of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizedForOffice Context triple: [2013 Presidential Inaugural Committee, organizedForOffice, President of the United States]
-
A.
worksWithOffice
Indicates that an entity collaborates or is professionally associated with a particular office or office-based organization.
-
B.
officeUnder
Indicates that one office is subordinate to, managed by, or organizationally within the authority of another office.
-
C.
office
Indicates that an entity holds or occupies an official position, role, or post within an organization or institution.
-
D.
officeStart
Indicates the time or date at which an entity’s term, role, or period of holding office begins.
-
E.
officeIsIn
Indicates that one office is located within or inside another specified place or building.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d26c621c8190a6eddc0d395e13e4 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d182213c819086fcbbfd3d64d80b |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:14 p.m.