Triple
T3981262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Section 5 of the Fourteenth Amendment |
E85762
|
entity |
| Predicate | grantsBranchPower |
P48020
|
FINISHED |
| Object | legislative branch |
—
|
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: legislative branch | Statement: [Section 5 of the Fourteenth Amendment, grantsBranchPower, legislative branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantsBranchPower Context triple: [Section 5 of the Fourteenth Amendment, grantsBranchPower, legislative branch]
-
A.
grantedPower
Indicates that one entity has conferred authority, control, or a specific capability to another entity.
-
B.
governmentBranchEmpowered
chosen
Indicates that a particular branch of government has been granted the authority or power to perform a specified function or exercise certain responsibilities.
-
C.
typeOfPowerGranted
Indicates the specific kind or category of power or authority that is conferred from one entity to another.
-
D.
grantedConstitution
Indicates that an authority formally bestowed or established a constitution for a political entity or organization.
-
E.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over another entity.
- 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_69aed93908348190a26c8aaf4fab3e86 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa3ef7ac8190abe02f440ff83c43 |
completed | March 9, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69aef8f492ac819089dbb9436dbcdd2b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.