Triple
T34774404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halevi |
E1002461
|
entity |
| Predicate | traditionalRoleAssociation |
P101409
|
FINISHED |
| Object | Temple service in ancient Israel |
—
|
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: Temple service in ancient Israel | Statement: [Halevi, traditionalRoleAssociation, Temple service in ancient Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalRoleAssociation Context triple: [Halevi, traditionalRoleAssociation, Temple service in ancient Israel]
-
A.
basisRole
Indicates that one role serves as the foundational or underlying role upon which another role or function is defined or derived.
-
B.
canonicalRole
Indicates that an entity holds a standard, primary, or officially recognized role within a particular context or system.
-
C.
traditionalAffiliation
chosen
Indicates a relationship where an entity is associated with another through long-established, customary, or historically rooted ties or membership.
-
D.
ordinationRole
Indicates the specific religious or ceremonial office, function, or capacity in which an entity is formally ordained.
-
E.
recognizedRole
Indicates that one entity acknowledges or accepts another entity’s role, position, or function within a given context.
- 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_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
Created at: May 3, 2026, 3:59 p.m.