Triple
T3505709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of the United Kingdom |
E74069
|
entity |
| Predicate | entrenchment |
P11185
|
FINISHED |
| Object | largely unentrenched |
—
|
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: largely unentrenched | Statement: [Constitution of the United Kingdom, entrenchment, largely unentrenched]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entrenchment Context triple: [Constitution of the United Kingdom, entrenchment, largely unentrenched]
-
A.
entrenched
chosen
Indicates that something is firmly and deeply established in a position, practice, or condition, making it difficult to change or remove.
-
B.
binding
Indicates that one entity physically or chemically attaches, adheres, or forms a stable association with another entity.
-
C.
traction
Indicates the degree to which one entity’s movement or influence effectively grips, pulls, or gains momentum relative to another entity or medium.
-
D.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
-
E.
holding
Indicates that one entity is physically grasping, carrying, or keeping another entity in its possession or control.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbf38e988190998d722b95830411 |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0e770481908528fa35eda53003 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.