Triple
T4004369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gustav I of Sweden |
E89487
|
entity |
| Predicate | seized |
P5949
|
FINISHED |
| Object | church lands and properties in Sweden |
—
|
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: church lands and properties in Sweden | Statement: [Gustav I of Sweden, seized, church lands and properties in Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seized Context triple: [Gustav I of Sweden, seized, church lands and properties in Sweden]
-
A.
seizedPowerBy
Indicates that one entity took control or authority from another, typically through force, coercion, or other non-consensual means.
-
B.
confiscatedBy
chosen
Indicates that something has been taken away and seized by an authority or agent, typically as a legal or disciplinary action.
-
C.
hijacked
Indicates that one entity has forcibly taken control of another entity, typically without authorization and against the will of its rightful controller.
-
D.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
-
E.
seal
Indicates that an agent closes or fastens something so that it is securely shut and often airtight or watertight.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa8579288190940487ad07e38de0 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8f89f2881909b0965419d15d46c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.