Triple

T19308667
Position Surface form Disambiguated ID Type / Status
Subject Latin Europe E482907 entity
Predicate sharedLegalTradition P17298 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: [Latin Europe, sharedLegalTradition, civil law]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sharedLegalTradition
Context triple: [Latin Europe, sharedLegalTradition, civil law]
  • A. coexistingLegalTradition
    Indicates that multiple legal traditions or systems exist and operate simultaneously within the same social or institutional context.
  • B. hasLawTradition chosen
    Indicates that one legal system, jurisdiction, or entity follows or is based on a particular legal tradition or family of law.
  • C. legalTraditionInfluenced
    Indicates that one legal tradition has had a formative or shaping influence on the development, principles, or practices of another legal tradition.
  • D. legalTraditionsTaught
    Indicates that one entity teaches, covers, or includes specific legal traditions in its instruction or curriculum.
  • E. customaryLaw
    Indicates that a relationship, behavior, or rule is governed by unwritten, traditional norms and practices recognized as binding within a community or group.
  • 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_69d8e8d04d5c8190baa816986f2b1d1e completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e604cb47c88190bd01e6f5f4d2204f completed April 20, 2026, 10:49 a.m.
PD Predicate disambiguation batch_69e4dd0ef66881909d489d634eee817a completed April 19, 2026, 1:47 p.m.
Created at: April 10, 2026, 1:32 p.m.