Triple
T4767920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zechariah |
E105856
|
entity |
| Predicate | spouseLineage |
P25212
|
FINISHED |
| Object | descendant of Aaron |
—
|
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: descendant of Aaron | Statement: [Zechariah, spouseLineage, descendant of Aaron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseLineage Context triple: [Zechariah, spouseLineage, descendant of Aaron]
-
A.
spouseDynasty
chosen
Indicates that there is a marital relationship linking an entity to the dynasty (family line or ruling house) of their spouse.
-
B.
spouseParentage
Indicates that one entity is a parent of the other entity’s spouse.
-
C.
spouseFamily
Indicates a family relationship formed through marriage, such as between a person and their spouse’s relatives.
-
D.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
E.
spouseOfHead
Indicates that one person is the married partner of the individual who holds the position of head (e.g., head of a household, organization, or state).
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.