Triple
T34765276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ine of Wessex |
E1002192
|
entity |
| Predicate | lawCodeFeatures |
P25070
|
FINISHED |
| Object | provisions on compensation (wergild) |
—
|
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: provisions on compensation (wergild) | Statement: [Ine of Wessex, lawCodeFeatures, provisions on compensation (wergild)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lawCodeFeatures Context triple: [Ine of Wessex, lawCodeFeatures, provisions on compensation (wergild)]
-
A.
legalFeature
Indicates that something possesses a specific legal characteristic, status, or attribute relevant to laws or regulations.
-
B.
legalSystemFeature
chosen
Indicates a characteristic, rule, or structural element that forms part of a particular legal system.
-
C.
featuresLaw
Indicates that something includes, presents, or is characterized by a particular law or legal provision.
-
D.
lawCharacteristicInText
Indicates that a specific legal characteristic or feature is expressed, described, or referenced within a given text.
-
E.
lawCollection
Indicates a relationship in which a set of legal rules, statutes, or regulations is grouped or organized together as a collection.
- 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_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 3:59 p.m.