Triple
T6264765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Horsemen (Supreme Court) |
E140386
|
entity |
| Predicate | positionOnNewDeal |
P69047
|
FINISHED |
| Object | opposed key New Deal legislation |
—
|
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: opposed key New Deal legislation | Statement: [Four Horsemen (Supreme Court), positionOnNewDeal, opposed key New Deal legislation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnNewDeal Context triple: [Four Horsemen (Supreme Court), positionOnNewDeal, opposed key New Deal legislation]
-
A.
positionOfDeclarer
Indicates the relative seat or role that the declarer occupies in a turn-based or positional setting.
-
B.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
positionOnNegotiations
Indicates the stance or viewpoint an entity holds regarding a particular negotiation or set of negotiations.
-
E.
positionInSettlement
Indicates the specific location or placement of an entity within the boundaries or layout of a settlement.
- 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_69c008cabc4081909723e2547c9d6cc0 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0638c43808190a375e9f29f2b2138 |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05606fb50819082d1a5a91e5030b6 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c965ac8190b938502fa8c74e1b |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:25 p.m.