Triple
T17011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Constitution |
E337
|
entity |
| Predicate | limits |
P99
|
FINISHED |
| Object | government power through enumerated powers |
—
|
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: government power through enumerated powers | Statement: [United States Constitution, limits, government power through enumerated powers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limits Context triple: [United States Constitution, limits, government power through enumerated powers]
-
A.
hasLimitation
chosen
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
B.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
C.
length
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
D.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
E.
near
Indicates that one entity is located at a short distance from another entity in space or position.
- 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a241ea1ea081908e8a81ca97531ba5 |
completed | Feb. 28, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69a23fec1fe8819080da6f2c745dc8fd |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.