Triple
T10164301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sisebut |
E233967
|
entity |
| Predicate | issuedLawRegarding |
P11901
|
FINISHED |
| Object | forced baptism of Jews |
—
|
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: forced baptism of Jews | Statement: [Sisebut, issuedLawRegarding, forced baptism of Jews]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuedLawRegarding Context triple: [Sisebut, issuedLawRegarding, forced baptism of Jews]
-
A.
legalAct
Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
-
B.
introducedInLaws
Indicates that one entity caused another entity to meet or become acquainted with their in-laws.
-
C.
enforcedLaw
chosen
Indicates that an authority actively applies or upholds a specific law to regulate behavior or resolve situations.
-
D.
associatedLawProclaimedAt
Indicates the date, time, or event at which a particular law or legal act was formally proclaimed or officially announced.
-
E.
legalCodePromulgatedBy
Indicates that a specific legal code was formally issued or enacted by a particular authority or governing body.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec6b96dc8190ae37d0d28e4c393b |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:09 p.m.