Triple
T11647803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ex parte Merryman |
E276818
|
entity |
| Predicate | branchChallenged |
P100172
|
FINISHED |
| Object | executive branch |
—
|
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: executive branch | Statement: [Ex parte Merryman, branchChallenged, executive branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchChallenged Context triple: [Ex parte Merryman, branchChallenged, executive branch]
-
A.
stateActionChallenged
Indicates that an action taken by a state (or state authority) has been formally disputed, questioned, or contested by another party.
-
B.
laterChallengedBy
Indicates that an earlier claim, decision, or position was subsequently questioned, disputed, or opposed by another party.
-
C.
stateChallenged
Indicates that a state or condition is being questioned, disputed, or formally contested by another party.
-
D.
canBeChallengedOn
Indicates that one entity’s claim, decision, or status is open to being questioned, disputed, or formally contested by another entity.
-
E.
hasBeenChallengedIn
Indicates that an entity has faced a challenge, contest, or dispute within a specified context, domain, or setting.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cd9bb0819093d107204bed2fe0 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
| PDg | Predicate description generation | batch_69d87f30642c8190ad94fa061cde186b |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:39 p.m.