Triple
T34774405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halevi |
E1002461
|
entity |
| Predicate | denotesAncestry |
P55649
|
FINISHED |
| Object | membership in Levite tribe |
—
|
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: membership in Levite tribe | Statement: [Halevi, denotesAncestry, membership in Levite tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesAncestry Context triple: [Halevi, denotesAncestry, membership in Levite tribe]
-
A.
typeOfAncestry
Indicates that one entity’s ancestry or lineage is characterized as being of a particular type or origin in relation to another entity.
-
B.
ancestralStatus
chosen
Indicates that one entity holds a particular ancestral or lineage-based relationship or status in relation to another entity.
-
C.
isAncestralNameOf
Indicates that one name is historically or genealogically derived from, or serves as the origin for, another name.
-
D.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
E.
mayIndicateAncestralOriginFrom
Indicates that one entity suggests or implies the ancestral origin or lineage of another 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_69f76db30a108190bb57ca95b873e5bb |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 3:59 p.m.