Triple
T3882615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSC 10/2 directive |
E92859
|
entity |
| Predicate | approvedByOffice |
P807
|
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: [NSC 10/2 directive, approvedByOffice, President of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approvedByOffice Context triple: [NSC 10/2 directive, approvedByOffice, President of the United States]
-
A.
approvedBy
chosen
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
B.
approvedAt
Indicates the date and time at which an entity received formal approval.
-
C.
approvalStatus
Indicates the current state of authorization or acceptance granted to an entity or action.
-
D.
approvalProcess
Indicates the sequence of steps, decisions, and authorizations required for something to be formally reviewed and approved.
-
E.
approves
Indicates that one entity formally accepts, authorizes, or agrees to a proposal, action, or decision made by another entity.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7574c408190893e70bf80514838 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.