Triple
T24911115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherwin Wine |
E623845
|
entity |
| Predicate | religiousMovementFounded |
P8499
|
FINISHED |
| Object | Humanistic Judaism |
—
|
NE NERFINISHED |
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: Humanistic Judaism | Statement: [Sherwin Wine, religiousMovementFounded, Humanistic Judaism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousMovementFounded Context triple: [Sherwin Wine, religiousMovementFounded, Humanistic Judaism]
-
A.
religiousMovementLed
Indicates that one entity serves as the leader or guiding figure of a particular religious movement.
-
B.
religiousMovementOrigin
Indicates that a religious movement began, was founded, or first emerged in a particular place or context.
-
C.
foundedReligion
chosen
Indicates that an entity established or originated a particular religion.
-
D.
hasReligiousMovementTypeFoundedThere
Indicates that a particular religious movement was founded or originated at the referenced location.
-
E.
hasReligiousFounderAssociated
Indicates that an entity is associated with a specific religious founder, typically through origin, dedication, or foundational influence.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 5:28 a.m.