Triple
T640331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life Peerages Act 1958 |
E16723
|
entity |
| Predicate | enablesCreationOf |
P273
|
FINISHED |
| Object | life peers |
—
|
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: life peers | Statement: [Life Peerages Act 1958, enablesCreationOf, life peers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesCreationOf Context triple: [Life Peerages Act 1958, enablesCreationOf, life peers]
-
A.
supportedCreationOf
Indicates that one entity actively aided, endorsed, or facilitated the bringing into existence or establishment of another entity.
-
B.
hasCreation
Indicates a relationship where one entity is the creator or originator of another entity.
-
C.
canMake
Indicates that one entity has the ability or capacity to create, produce, or assemble another entity.
-
D.
canEnforce
Indicates that one entity has the authority or capability to compel compliance with rules, decisions, or obligations upon another entity.
-
E.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f0189b08190a584b744f36fa761 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0830008190a26ee158ed4dd1fe |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.