Triple
T396963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article V |
E9203
|
entity |
| Predicate | sectionOf |
P3120
|
FINISHED |
| Object | original unamended Constitution |
—
|
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: original unamended Constitution | Statement: [Article V, sectionOf, original unamended Constitution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionOf Context triple: [Article V, sectionOf, original unamended Constitution]
-
A.
section
chosen
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
B.
section7Provides
Indicates that Section 7 serves as the source or provider of something (such as rights, obligations, benefits, or content) to another party or element.
-
C.
isSectionNumber
Indicates that one entity is the section number identifier associated with another entity, typically within a structured document or text.
-
D.
streetSectionOf
Indicates that one street segment or portion belongs to, is contained within, or forms part of a larger street or roadway.
-
E.
notableSectionNear
Indicates that one section or segment is located physically close to another section or segment in a way that is noteworthy or significant.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ec8a941081909a152fda0ce24a98 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96d17d08190878d3a68b17d51ca |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.