Triple
T131482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White House Office of the Chief Usher |
E2662
|
entity |
| Predicate | nonPartisan |
P6897
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [White House Office of the Chief Usher, nonPartisan, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonPartisan Context triple: [White House Office of the Chief Usher, nonPartisan, true]
-
A.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
traditionalPoliticalAlignment
Indicates how closely an entity’s political views or affiliations align with established, historically dominant, or customary political positions within a given context.
-
C.
nationalCommittee
Indicates that an entity serves as or is associated with a national-level committee or governing body for another entity.
-
D.
politicalParty
Indicates that an entity is affiliated with, belongs to, or is a member of a specific political party.
-
E.
dominantParty
Indicates that one party in a relationship holds primary control, authority, or influence over the other.
- 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_69a25855baf48190a1b63f2e5865d957 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2564edb488190974dc00eb9ac37d9 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2585408c881908a25b5c61f300154 |
completed | Feb. 28, 2026, 2:52 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.