Triple
T2306657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statute of Mortmain |
E51854
|
entity |
| Predicate | aimedAtPreventing |
P17548
|
FINISHED |
| Object | loss of feudal incidents to lords |
—
|
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: loss of feudal incidents to lords | Statement: [Statute of Mortmain, aimedAtPreventing, loss of feudal incidents to lords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimedAtPreventing Context triple: [Statute of Mortmain, aimedAtPreventing, loss of feudal incidents to lords]
-
A.
aimsToProtect
Indicates an intention or purpose to safeguard or defend one entity, value, or condition from harm, risk, or undesirable outcomes.
-
B.
prevented
Indicates that one entity stopped, hindered, or made it impossible for another entity or event to occur or proceed.
-
C.
worksToPrevent
Indicates an entity actively takes measures or engages in actions to stop, reduce, or avoid the occurrence or impact of another entity or condition.
-
D.
designedToAvoid
chosen
Indicates that something was intentionally created or configured in a way that prevents or minimizes a particular outcome, condition, or interaction.
-
E.
enactedInResponseTo
Indicates that one action, policy, or measure was carried out as a direct reaction to a specific prior event, condition, or stimulus.
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abce1f4f0c8190a714e4dcb8449f7e |
completed | March 7, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69abc58ce2a081908ce2f0cadd92e9f8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.