Triple
T1284930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article VI, Clause 2 of the U.S. Constitution |
E27412
|
entity |
| Predicate | textContains |
P6841
|
FINISHED |
| Object | "shall be the supreme Law of the Land" |
—
|
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: "shall be the supreme Law of the Land" | Statement: [Article VI, Clause 2 of the U.S. Constitution, textContains, "shall be the supreme Law of the Land"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textContains Context triple: [Article VI, Clause 2 of the U.S. Constitution, textContains, "shall be the supreme Law of the Land"]
-
A.
containsText
chosen
Indicates that one entity includes the specified text string within its content.
-
B.
containsCharacter
Indicates that one entity includes a specific character as part of its content or composition.
-
C.
containsFinding
Indicates that one entity includes, encompasses, or holds a particular finding as part of its content or results.
-
D.
followsInText
Indicates that one textual element appears immediately or subsequently after another within the same text.
-
E.
containsLine
Indicates that one entity includes or encloses a specific line within its spatial or structural extent.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0b6dda48190a2e79084adea6ec1 |
completed | March 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69a4bee276d8819092f71c5a1140bb61 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.