Triple
T14298052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Constitution Article I Section 8 Clause 4 |
E354490
|
entity |
| Predicate | numberedWithinSection |
P22578
|
FINISHED |
| Object | Clause 4 |
—
|
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: Clause 4 | Statement: [United States Constitution Article I Section 8 Clause 4, numberedWithinSection, Clause 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberedWithinSection Context triple: [United States Constitution Article I Section 8 Clause 4, numberedWithinSection, Clause 4]
-
A.
isSectionNumber
Indicates that one entity is the section number identifier associated with another entity, typically within a structured document or text.
-
B.
isNumbered
chosen
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
-
C.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
D.
isNamedSectionOf
Indicates that one entity is a specifically named section or subdivision that forms part of another entity.
-
E.
numberingReason
Indicates the rationale or basis for assigning a particular number or numbering scheme to something.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de717cfc948190ace5f1c91283b1c3 |
completed | April 14, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:11 a.m.