Triple

T204512
Position Surface form Disambiguated ID Type / Status
Subject United States federal law E4581 entity
Predicate supremacyOver P2949 FINISHED
Object conflicting state laws 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: conflicting state laws | Statement: [United States federal law, supremacyOver, conflicting state laws]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supremacyOver
Context triple: [United States federal law, supremacyOver, conflicting state laws]
  • A. supremacyClause chosen
    Indicates that one legal authority, rule, or agreement takes precedence over and invalidates conflicting lower-level laws or provisions.
  • B. exercisedPowerOver
    Indicates that one entity exerted control, influence, or authority over another entity.
  • C. hasSupremeOffice
    Indicates that an entity holds or occupies the highest-ranking official position within a given organization, institution, or jurisdiction.
  • D. superlative
    Indicates that one entity possesses a property to the greatest or least degree when compared with all others in a given set.
  • E. suzerain
    Indicates a relationship in which one entity holds overlordship or supreme authority over another, which remains internally autonomous but owes allegiance, tribute, or obedience.
  • 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.