Triple
T19784491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abner son of Ner |
E475223
|
entity |
| Predicate | loyaltyShiftReason |
P91356
|
FINISHED |
| Object | quarrel with Ish-bosheth over Rizpah |
—
|
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: quarrel with Ish-bosheth over Rizpah | Statement: [Abner son of Ner, loyaltyShiftReason, quarrel with Ish-bosheth over Rizpah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyShiftReason Context triple: [Abner son of Ner, loyaltyShiftReason, quarrel with Ish-bosheth over Rizpah]
-
A.
loyaltyReason
Indicates the reason or motivation behind one entity’s loyalty or allegiance to another.
-
B.
loyaltyChange
chosen
Indicates a change in the degree or direction of loyalty from one entity toward another over time.
-
C.
loyaltyDimension
Indicates the degree or aspect of loyalty characterizing the relationship between entities.
-
D.
loyaltyIncentive
Indicates a relationship where benefits or rewards are provided to encourage or recognize continued commitment or repeat engagement.
-
E.
loyaltyArc
Indicates a character’s progression in loyalty toward another entity, typically showing how trust, allegiance, or faithfulness strengthens, weakens, or transforms over time.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538715b8819080c6930e7d16ab58 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.