Triple
T10370696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Recceswinth |
E244373
|
entity |
| Predicate | legalCodeScope |
P25835
|
FINISHED |
| Object | civil 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: civil law | Statement: [Recceswinth, legalCodeScope, civil law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalCodeScope Context triple: [Recceswinth, legalCodeScope, civil law]
-
A.
legalCodeAppliesTo
Indicates that a particular legal code or statute is applicable to, or governs, a specified subject, situation, or entity.
-
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.
legalCodeType
Indicates the specific category or classification of a legal code that applies to an entity or situation.
-
D.
legalCodeAvailableAt
Indicates that a particular legal code or statute can be accessed, obtained, or consulted at a specified source or location.
-
E.
legalScope
chosen
Indicates the range, boundaries, or extent of authority, applicability, or effect that something has under a particular legal framework or rule.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9737cfc81909d6302bd4177d186 |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:01 p.m.