Triple
T204545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States federal law |
E4581
|
entity |
| Predicate | includesPrinciple |
P1393
|
FINISHED |
| Object | federal preemption |
—
|
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: federal preemption | Statement: [United States federal law, includesPrinciple, federal preemption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPrinciple Context triple: [United States federal law, includesPrinciple, federal preemption]
-
A.
usesPrinciple
Indicates that one entity applies, relies on, or is based upon a particular principle in its functioning, reasoning, or design.
-
B.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
C.
violatedPrinciple
Indicates that an entity has broken, disregarded, or acted contrary to a specified rule, norm, or guiding principle.
-
D.
constitutionalPrinciple
Indicates that something embodies, expresses, or is governed by a fundamental rule or doctrine within a constitutional system.
-
E.
formationPrinciple
Indicates the underlying rule, pattern, or principle according to which something is formed, structured, or brought into existence.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f46b4f081909e5ee3718109a71f |
completed | Feb. 28, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69a25b4b42ec8190bef16bbbdd30a742 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.