Triple
T25782404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KC-45A |
E649324
|
entity |
| Predicate | protestUpheldBy |
P1123
|
FINISHED |
| Object | U.S. Government Accountability Office |
—
|
NE NERFINISHED |
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: U.S. Government Accountability Office | Statement: [KC-45A, protestUpheldBy, U.S. Government Accountability Office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protestUpheldBy Context triple: [KC-45A, protestUpheldBy, U.S. Government Accountability Office]
-
A.
upheldBy
chosen
Indicates that one entity is supported, maintained, or validated by another, often through approval, enforcement, or confirmation of its validity.
-
B.
protests
Indicates that an entity publicly expresses opposition or disapproval toward another entity, action, or situation.
-
C.
notableProtest
Indicates that an entity is recognized for having led, organized, or been centrally involved in a significant protest or demonstration.
-
D.
protestFocus
Indicates that a protest is directed toward, concerned with, or centered on a particular issue, target, or subject.
-
E.
protestForm
Indicates the specific method or mode by which a protest or demonstration is carried out.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fe6175048190afd845628c74830e |
completed | May 2, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 5:51 a.m.