Triple
T16946611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raków |
E411082
|
entity |
| Predicate | postSuppressionOutcome |
P125338
|
FINISHED |
| Object | dispersion of Socinian scholars |
—
|
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: dispersion of Socinian scholars | Statement: [Raków, postSuppressionOutcome, dispersion of Socinian scholars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postSuppressionOutcome Context triple: [Raków, postSuppressionOutcome, dispersion of Socinian scholars]
-
A.
postContactOutcome
Indicates the result or status that occurs after a contact or interaction has taken place.
-
B.
suppressedOn
Indicates that one entity is intentionally prevented, hidden, or blocked from being shown, executed, or taking effect in the context of another entity.
-
C.
postMergerStatus
Indicates the status or condition of an entity following the completion of a merger.
-
D.
orderedSuppressionOf
Indicates that one entity has formally directed or mandated the suppression, restriction, or silencing of another entity or its actions.
-
E.
suppressedFollowing
Indicates that one entity’s act of following another has been intentionally hidden, blocked, or not allowed to occur.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb25e0c8190948e62d9575ae9cd |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:31 a.m.