Triple
T34376824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qedemah |
E882307
|
entity |
| Predicate | birthOrderContext |
P20593
|
FINISHED |
| Object | one of the twelve sons of Ishmael |
—
|
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: one of the twelve sons of Ishmael | Statement: [Qedemah, birthOrderContext, one of the twelve sons of Ishmael]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthOrderContext Context triple: [Qedemah, birthOrderContext, one of the twelve sons of Ishmael]
-
A.
positionInFamilyBirthOrder
chosen
Indicates the relative order in which a person was born within their family (e.g., first-born, middle child, last-born).
-
B.
orderOfBirth
Indicates the relative sequence in which entities are born, specifying who is earlier or later in birth order.
-
C.
bornAfter
Indicates that one entity’s birth occurred later in time than another entity’s birth.
-
D.
positionInLineOfSuccessionAtBirth
Indicates the ordinal place an individual held in a defined line of succession at the moment of their birth.
-
E.
born
Indicates that an entity comes into existence at a specific time and place, typically from parent entities.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 1:59 a.m.