Triple
T32945680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beorhtwulf of Mercia |
E842792
|
entity |
| Predicate | legalActs |
P10360
|
FINISHED |
| Object | land grants to lay nobles |
—
|
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: land grants to lay nobles | Statement: [Beorhtwulf of Mercia, legalActs, land grants to lay nobles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalActs Context triple: [Beorhtwulf of Mercia, legalActs, land grants to lay nobles]
-
A.
legalAct
chosen
Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
-
B.
legalAuthorityIn
Indicates that an entity holds official legal power, jurisdiction, or governing authority within a specified area or domain.
-
C.
legalElement
Indicates that something is a constituent part or component required or recognized within a legal framework, rule, or process.
-
D.
legalIn
Indicates that an action, status, or entity is permitted or valid under the laws or regulations of a specified jurisdiction.
-
E.
legalMatters
Indicates that one entity is involved with, concerned about, or responsible for legal issues, processes, or obligations related to another entity or context.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: May 1, 2026, 1:20 a.m.