Triple
T3142313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Issachar |
E65677
|
entity |
| Predicate | religiousCulture |
P9028
|
FINISHED |
| Object | Israelite |
—
|
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: Israelite | Statement: [Issachar, religiousCulture, Israelite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousCulture Context triple: [Issachar, religiousCulture, Israelite]
-
A.
religiousTraditions
Indicates a relationship where certain religious customs, practices, or belief systems are associated with or observed by an entity.
-
B.
religiousCulturalContext
chosen
Indicates the religious or cultural setting, tradition, or framework within which an entity, practice, or event occurs or is interpreted.
-
C.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
D.
ethnicReligion
Indicates that a religion is closely associated with a particular ethnic group, often tied to that group’s culture, ancestry, or identity.
-
E.
laterReligion
Indicates that one religion or religious affiliation chronologically follows or replaces another for the same entity.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada579b07c8190a7b316f499911a2d |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.