Triple
T14892460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everyman |
E359784
|
entity |
| Predicate | protagonistReligionOrCulture |
P83945
|
FINISHED |
| Object | Jewish American |
—
|
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: Jewish American | Statement: [Everyman, protagonistReligionOrCulture, Jewish American]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistReligionOrCulture Context triple: [Everyman, protagonistReligionOrCulture, Jewish American]
-
A.
religionOfCharacterPortrayed
chosen
Indicates that a work portrays a character as adhering to or being associated with a particular religion.
-
B.
portraysReligionAs
Indicates that one entity represents, depicts, or characterizes a religion in a particular way.
-
C.
religionInBackstory
Indicates that a character’s religious beliefs or practices play a role in their past or origin story.
-
D.
religiousCulturalContext
Indicates the religious or cultural setting, tradition, or framework within which an entity, practice, or event occurs or is interpreted.
-
E.
religionOrBelief
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded5f883288190af602633fa7d6860 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:10 a.m.