Triple
T31142557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ossory |
E793827
|
entity |
| Predicate | medievalLaw |
P15549
|
FINISHED |
| Object | Brehon law |
—
|
NE NERFINISHED |
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: Brehon law | Statement: [Ossory, medievalLaw, Brehon law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: medievalLaw Context triple: [Ossory, medievalLaw, Brehon law]
-
A.
historicalLaw
chosen
Indicates that the referenced law or legal provision existed and was in effect during a past historical period, rather than being current.
-
B.
medievalLordship
Indicates a feudal relationship in which one entity holds authority, control, or dominion over another in a medieval lord–vassal or territorial context.
-
C.
medievalStatus
Indicates the social, legal, or hierarchical standing an entity holds within a medieval societal structure.
-
D.
medievalState
Indicates that an entity functioned as a state or political unit during the medieval historical period.
-
E.
medievalSeeTransferredTo
Indicates that authority, ownership, or jurisdiction over a medieval ecclesiastical see was formally transferred from one holder or location to another.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:06 p.m.