Triple
T2287627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statute of Quia Emptores |
E51429
|
entity |
| Predicate | permitted |
P273
|
FINISHED |
| Object | substitution of tenants by alienation |
—
|
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: substitution of tenants by alienation | Statement: [Statute of Quia Emptores, permitted, substitution of tenants by alienation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permitted Context triple: [Statute of Quia Emptores, permitted, substitution of tenants by alienation]
-
A.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
B.
permitType
Indicates the specific category or kind of permit associated with an entity or activity.
-
C.
allowedReturn
Indicates that an entity is permitted to be returned or sent back under specified conditions or rules.
-
D.
grantedIn
Indicates that something (such as a right, status, or permission) is formally conferred or authorized within a particular context, document, or jurisdiction.
-
E.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc24868048190940512fd6449d99e |
completed | March 7, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69abbdbb9e4c819085fc588626ec7c09 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.