Triple
T33929460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semen |
E869845
|
entity |
| Predicate | hasBiblicalRoot |
P172821
|
FINISHED |
| Object | Simeon |
—
|
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: Simeon | Statement: [Semen, hasBiblicalRoot, Simeon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBiblicalRoot Context triple: [Semen, hasBiblicalRoot, Simeon]
-
A.
hasBiblicalConnection
Indicates a relationship in which one entity is connected to another through references, themes, origins, or influences derived from the Bible.
-
B.
hasBiblicalEthnonym
chosen
Indicates that an entity is associated with or identified by an ethnonym (a people or ethnic group name) that originates from or is used within the Bible.
-
C.
hasReligiousOrigin
Indicates that something originates from, is derived from, or is fundamentally based on a religious tradition, belief system, or practice.
-
D.
isBiblicalVariantOf
Indicates that one textual form or reading is a variant version of another within the biblical textual tradition.
-
E.
hasPrimaryBiblicalText
Indicates that one entity is associated with another entity that serves as its main or authoritative biblical text.
- 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: May 1, 2026, 1:49 a.m.