Triple
T507747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill of Rights |
E10538
|
entity |
| Predicate | numberOfAmendments |
P1039
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Bill of Rights, numberOfAmendments, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfAmendments Context triple: [Bill of Rights, numberOfAmendments, 10]
-
A.
amendmentCount
chosen
Indicates the number of amendments that have been made to a given item, document, or entity.
-
B.
hasAmendments
Indicates that one entity (such as a document, law, or agreement) includes or is associated with one or more modifications, changes, or additions made after its original creation.
-
C.
constitutionalChange
Indicates a formal modification, addition, or removal of provisions within a constitution or foundational legal framework.
-
D.
effectOfAmendments
Indicates the causal impact or consequences that specific amendments have on something, such as a law, document, or situation.
-
E.
laterConstitutionalAct
Indicates that one constitutional act occurs after another in time, establishing a later legal or constitutional measure relative to a prior one.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f14dcd688190ad47a3b31b95b6d4 |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfce7a08190a408bc019de60d5d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.