Triple
T4767133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burgundian Kingdom (early phase) |
E105840
|
entity |
| Predicate | legalPolicy |
P22522
|
FINISHED |
| Object | separate laws for Romans and Burgundians |
—
|
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: separate laws for Romans and Burgundians | Statement: [Burgundian Kingdom (early phase), legalPolicy, separate laws for Romans and Burgundians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalPolicy Context triple: [Burgundian Kingdom (early phase), legalPolicy, separate laws for Romans and Burgundians]
-
A.
lawStatement
chosen
Indicates that an entity expresses, codifies, or articulates a legal rule, principle, or requirement.
-
B.
governingPolicy
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
-
C.
policyLanguage
Indicates the specific wording or formulation used within a policy to express its rules, conditions, or provisions.
-
D.
explainsPolicy
Indicates that one entity provides a clarification or detailed description of a policy to another entity.
-
E.
dataPolicy
Indicates that one entity defines or governs how data related to another entity is collected, used, stored, or shared.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.