Triple
T3745225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korah |
E81193
|
entity |
| Predicate | descendantsAssociatedWith |
P39094
|
FINISHED |
| Object | Levitical temple service |
—
|
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: Levitical temple service | Statement: [Korah, descendantsAssociatedWith, Levitical temple service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: descendantsAssociatedWith Context triple: [Korah, descendantsAssociatedWith, Levitical temple service]
-
A.
associatedWithDescendants
chosen
Indicates that an entity has a relationship or connection specifically involving the descendants of another entity.
-
B.
hasDescendantPeople
Indicates that one entity has other people as its descendants in a genealogical or lineage-based relationship.
-
C.
associatedHeir
Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
-
D.
associatedWithPatriarch
Indicates that an entity has a relationship, connection, or affiliation with a patriarch, such as being under their authority, influence, or domain.
-
E.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb680ddc819094205beb342699f9 |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.