Triple
T1144940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justinian I |
E23541
|
entity |
| Predicate | legalTraditionInfluenced |
P24435
|
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: [Justinian I, legalTraditionInfluenced, civil law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalTraditionInfluenced Context triple: [Justinian I, legalTraditionInfluenced, civil law]
-
A.
legalDoctrineInfluenced
Indicates that one legal doctrine has shaped, informed, or contributed to the development or interpretation of another legal doctrine.
-
B.
hasLawTradition
Indicates that one legal system, jurisdiction, or entity follows or is based on a particular legal tradition or family of law.
-
C.
legalTraditionsTaught
Indicates that one entity teaches, covers, or includes specific legal traditions in its instruction or curriculum.
-
D.
coexistingLegalTradition
Indicates that multiple legal traditions or systems exist and operate simultaneously within the same social or institutional context.
-
E.
legalDoctrine
Indicates that one legal principle, rule, or theory is being applied, referenced, or relied upon as an authoritative basis for interpreting or deciding a legal issue.
- F. None of above. chosen
Provenance (4 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc51244c8190bcd533f3e80c8f17 |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4d4104819084027a043c6118cb |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bbb9fb4c81909dd39c496893c21b |
completed | March 1, 2026, 10:20 p.m. |
Created at: March 1, 2026, 7:44 p.m.