Triple
T20216971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De synodo dioecesana |
E495151
|
entity |
| Predicate | typeOfLawDiscussed |
P6527
|
FINISHED |
| Object | particular 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: particular law | Statement: [De synodo dioecesana, typeOfLawDiscussed, particular law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLawDiscussed Context triple: [De synodo dioecesana, typeOfLawDiscussed, particular law]
-
A.
typeOfLaw
chosen
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
-
B.
branchOfLaw
Indicates a relationship where one legal field or discipline is a subdivision or specialized area within a broader body of law.
-
C.
subjectOfLaw
Indicates that a law, legal document, or legal provision is about, concerns, or applies to the referenced subject.
-
D.
litigationType
Indicates the specific category or nature of a legal dispute or court case associated with an entity or event.
-
E.
legalMatters
Indicates that one entity is involved with, concerned about, or responsible for legal issues, processes, or obligations related to another entity or context.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66eda2f188190adf39d895e8b99f2 |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.