Triple
T7466400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baptism of Poland |
E176382
|
entity |
| Predicate | hasLegalImpact |
P39579
|
FINISHED |
| Object | introduction of Christian norms of 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: introduction of Christian norms of law | Statement: [Baptism of Poland, hasLegalImpact, introduction of Christian norms of law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalImpact Context triple: [Baptism of Poland, hasLegalImpact, introduction of Christian norms of law]
-
A.
hasLegalEffect
Indicates that an action, document, or condition produces recognized legal consequences or enforceable rights and obligations.
-
B.
impactOnLaw
chosen
Indicates the effect or influence that one entity, event, or action has on laws, legal rules, or the legal system.
-
C.
hasLegalRelevanceIn
Indicates that something is legally significant, applicable, or has consequences within a specified legal context, case, or jurisdiction.
-
D.
hasLegalIssue
Indicates that an entity is involved in, associated with, or subject to a legal problem, dispute, or proceeding.
-
E.
hasLegalChange
Indicates that an entity has undergone or is associated with a modification in its legal status, rights, obligations, or regulatory conditions.
- 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_69c69f223fd88190b4c69b95d7cbeeda |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3f412908190ac910ecae682d6f6 |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:40 p.m.