Triple
T1334009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Ahaus |
E28705
|
entity |
| Predicate | hasSystemOfLaw |
P605
|
FINISHED |
| Object | feudal law |
—
|
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: feudal law | Statement: [Lord of Ahaus, hasSystemOfLaw, feudal law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSystemOfLaw Context triple: [Lord of Ahaus, hasSystemOfLaw, feudal law]
-
A.
legalSystem
chosen
Indicates the formal framework of laws, rules, and institutions that governs how legal matters are defined, interpreted, and enforced within a society or jurisdiction.
-
B.
legalSystemWorkedOn
Indicates that a legal system has been applied to, influenced, or modified by some agent or process.
-
C.
legalSystemFeature
Indicates a characteristic, rule, or structural element that forms part of a particular legal system.
-
D.
hasLawTradition
Indicates that one legal system, jurisdiction, or entity follows or is based on a particular legal tradition or family of law.
-
E.
separateLegalSystem
Indicates that one entity maintains its own distinct and independent legal system from another entity.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1e98900819092c54c0fb58b958a |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef174708190a07bbc697fe19a2d |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.