Triple
T34765274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ine of Wessex |
E1002192
|
entity |
| Predicate | lawCodeType |
P24436
|
FINISHED |
| Object | Anglo-Saxon law code |
—
|
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: Anglo-Saxon law code | Statement: [Ine of Wessex, lawCodeType, Anglo-Saxon law code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lawCodeType Context triple: [Ine of Wessex, lawCodeType, Anglo-Saxon law code]
-
A.
legalCodeType
chosen
Indicates the specific category or classification of a legal code that applies to an entity or situation.
-
B.
legalCodeName
Indicates that one entity is the official legal code designation or name assigned to another entity within a legal or regulatory system.
-
C.
legalCodePromulgatedBy
Indicates that a specific legal code was formally issued or enacted by a particular authority or governing body.
-
D.
legalStandardType
Indicates the specific type or category of legal standard that governs or applies to a given legal rule, decision, or evaluation.
-
E.
typeOfLaw
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.