Triple
T24324192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Joseph |
E613048
|
entity |
| Predicate | traditionalEthnonym |
P4709
|
FINISHED |
| Object | Israelites |
—
|
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: Israelites | Statement: [House of Joseph, traditionalEthnonym, Israelites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalEthnonym Context triple: [House of Joseph, traditionalEthnonym, Israelites]
-
A.
ethnonym
chosen
Indicates that one entity is the name of an ethnic group used to refer to the people associated with another entity.
-
B.
ethnonymSingular
Indicates that the subject is the singular form of an ethnonym (a name for a member of a specific ethnic or national group).
-
C.
isEthnonymic
Indicates that something (typically a name or term) is derived from or based on the name of an ethnic group or people.
-
D.
ethnonymRoot
Indicates that one term serves as the morphological or etymological root from which an ethnonym (a name for an ethnic group or people) is derived.
-
E.
ethnonymAttestedIn
Indicates that the name of an ethnic group (ethnonym) is documented or recorded in a specified source, context, or medium.
- 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_69e2d7db6d5c819091194918157a7c1f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292ae127881909ef1772278181ce3 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:53 a.m.