Triple
T16197998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabbi Tarfon |
E393117
|
entity |
| Predicate | tribalDescent |
P13151
|
FINISHED |
| Object | Priestly family (Kohen) |
—
|
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: Priestly family (Kohen) | Statement: [Rabbi Tarfon, tribalDescent, Priestly family (Kohen)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribalDescent Context triple: [Rabbi Tarfon, tribalDescent, Priestly family (Kohen)]
-
A.
tribeOrGens
chosen
Indicates a relationship where an entity belongs to, is associated with, or is identified as a particular tribe or gens (clan/lineage group).
-
B.
tribeProgenitorOf
Indicates that one entity is the original ancestor or founding progenitor from which a particular tribe or tribal group descends.
-
C.
hasTribalMembersFrom
Indicates that an entity includes or is composed of members originating from a specified tribe or tribal group.
-
D.
recognizedTribe
Indicates that a group is officially acknowledged as a tribe by a governing or authoritative body.
-
E.
tribalCode
Indicates that an entity is governed by, associated with, or identified according to a specific tribal legal or regulatory code.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e222dc6b1c8190a3d8a6451ed8b95a |
completed | April 17, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.