Triple
T15803190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legal history of Poland |
E383145
|
entity |
| Predicate | earlyLawBasedOn |
P120134
|
FINISHED |
| Object | Slavic customary 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: Slavic customary law | Statement: [Legal history of Poland, earlyLawBasedOn, Slavic customary law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlyLawBasedOn Context triple: [Legal history of Poland, earlyLawBasedOn, Slavic customary law]
-
A.
civilLawBasedOn
Indicates that a civil law, legal system, or legal provision is derived from, grounded in, or significantly influenced by another specified source of law or legal framework.
-
B.
legalFoundationPeriod
Indicates the time span during which a legal foundation, basis, or framework is formally valid or in effect.
-
C.
earlierLegalLanguage
Indicates that one piece of legal language predates another in time or version within a legal context.
-
D.
legalBasis
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
-
E.
foundationInLaw
Indicates that something is based on, justified by, or derives its authority from a specific law or legal framework.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b524835c8190ae286b2562f07756 |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e00e48d49c819081afccb02f9cf18b |
completed | April 15, 2026, 10:16 p.m. |
Created at: April 10, 2026, 4:48 a.m.