Triple
T2283510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishmaelites |
E51332
|
entity |
| Predicate | biblicalEthnonymType |
P4709
|
FINISHED |
| Object | collective tribal designation |
—
|
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: collective tribal designation | Statement: [Ishmaelites, biblicalEthnonymType, collective tribal designation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biblicalEthnonymType Context triple: [Ishmaelites, biblicalEthnonymType, collective tribal designation]
-
A.
biblicalName
Indicates that one entity is the name of a person, place, or concept as it appears in the Bible.
-
B.
ethnonym
chosen
Indicates that one entity is the name of an ethnic group used to refer to the people associated with another entity.
-
C.
religiousNamesake
Indicates that one entity serves as the religiously significant figure, concept, or object after which the other entity is named.
-
D.
nameInPhoenician
Indicates the representation of an entity’s name when written in the Phoenician language or script.
-
E.
exonymStatus
Indicates the status or classification of a name used in one language to refer to a place, people, or entity known by a different name in its own language.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc2445f388190af643878145f8249 |
completed | March 7, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69abbdbb9e4c819085fc588626ec7c09 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.