Triple
T129281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Deputy Secretary of Defense |
E2617
|
entity |
| Predicate | inauguralHolderStartDate |
P5162
|
FINISHED |
| Object | May 2, 1949 |
—
|
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: May 2, 1949 | Statement: [United States Deputy Secretary of Defense, inauguralHolderStartDate, May 2, 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inauguralHolderStartDate Context triple: [United States Deputy Secretary of Defense, inauguralHolderStartDate, May 2, 1949]
-
A.
inaugurationDate
Indicates the date on which an official ceremony formally installs a person into a specific office or position.
-
B.
inaugurationDay
Indicates the specific day on which a formal ceremony is held to induct someone into an official position or office.
-
C.
inaugurationYear
Indicates the calendar year in which an entity was formally inaugurated or officially brought into operation.
-
D.
officeHolderStartTime
Indicates the date and time at which an individual begins holding a particular office or position.
-
E.
presidentInaugurated
Indicates that an individual formally assumes the office of president through an official inauguration event at a specific time and place.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a2576518e0819096b35d8af7a4d1bd |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564da96c8190aa8204de25229c15 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a256c72f6c81909b619b90d829d86e |
completed | Feb. 28, 2026, 2:45 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.