Triple

T61034
Position Surface form Disambiguated ID Type / Status
Subject Necessary and Proper Clause E1212 entity
Predicate locatedAfter P4527 FINISHED
Object list of enumerated powers in Article I, Section 8 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: list of enumerated powers in Article I, Section 8 | Statement: [Necessary and Proper Clause, locatedAfter, list of enumerated powers in Article I, Section 8]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedAfter
Context triple: [Necessary and Proper Clause, locatedAfter, list of enumerated powers in Article I, Section 8]
  • A. locatedBetween
    Indicates that one entity is positioned spatially between two other reference entities.
  • B. namedAfter
    Indicates that one entity has been given its name in honor of, or derived from, another entity.
  • C. locatedAlong
    Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
  • D. positionOn
    Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
  • E. locatedIn
    Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
  • 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_69a24ba4f760819081f6638a3c70538a completed Feb. 28, 2026, 1:57 a.m.
NER Named-entity recognition batch_69a251a1b8ac8190b44be4c3c41e5681 completed Feb. 28, 2026, 2:23 a.m.
PD Predicate disambiguation batch_69a24ea0bec48190b2af1fb287e9e692 completed Feb. 28, 2026, 2:10 a.m.
PDg Predicate description generation batch_69a251a088f8819083797c2baf310c39 completed Feb. 28, 2026, 2:23 a.m.
Created at: Feb. 28, 2026, 2:02 a.m.