Triple
T33046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supremacy Clause |
E659
|
entity |
| Predicate | binds |
P1045
|
FINISHED |
| Object | judges in every state |
—
|
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: judges in every state | Statement: [Supremacy Clause, binds, judges in every state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: binds Context triple: [Supremacy Clause, binds, judges in every state]
-
A.
bindingOn
chosen
Indicates that one party is legally or formally obligated to follow, accept, or be governed by a decision, rule, or agreement established by another.
-
B.
meets
Indicates that two or more entities come together at the same place and time, typically for interaction or a shared purpose.
-
C.
matches
Indicates that two entities correspond to or are in agreement with each other according to some defined criteria or pattern.
-
D.
handles
Indicates that one entity is responsible for dealing with, managing, or taking care of another entity or task.
-
E.
attracts
Indicates that one entity exerts a force or influence that draws another entity toward it.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2496ffc548190b545f998cbebd5b9 |
completed | Feb. 28, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69a248717f5081909952a8c9ed1e1742 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.