Triple
T23392470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitnagdim |
E594054
|
entity |
| Predicate | oppositionBeganAround |
P15443
|
FINISHED |
| Object | 1770s |
—
|
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: 1770s | Statement: [Mitnagdim, oppositionBeganAround, 1770s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppositionBeganAround Context triple: [Mitnagdim, oppositionBeganAround, 1770s]
-
A.
oppositionPeriodStart
chosen
Indicates the point in time when a formal opposition or challenge against something begins.
-
B.
emergedInOppositionTo
Indicates that one entity came into existence or gained prominence specifically as a reaction or counter-movement against another entity.
-
C.
opposition
Indicates a relationship in which one entity actively resists, disagrees with, or is positioned against another entity, idea, or action.
-
D.
oppositionActivity
Indicates that one entity engages in actions or behaviors that resist, counter, or work against another entity, its goals, or its activities.
-
E.
oppositionStatus
Indicates that one entity’s stance, condition, or role is characterized by being against, resisting, or in conflict with another entity, proposal, or situation.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a49df4308190ab4ab31310af81ed |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:36 p.m.