Triple
T19837693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheba son of Bichri |
E476639
|
entity |
| Predicate | loyalSupportBase |
P44132
|
FINISHED |
| Object | northern tribes of 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: northern tribes of Israel | Statement: [Sheba son of Bichri, loyalSupportBase, northern tribes of Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyalSupportBase Context triple: [Sheba son of Bichri, loyalSupportBase, northern tribes of Israel]
-
A.
loyalistsBase
chosen
Indicates that a group of loyalists is based at, or primarily operates from, a particular location or base.
-
B.
isLoyalTo
Indicates that one entity consistently supports, respects, or remains faithful to another entity.
-
C.
IndependentSupportBase
Indicates that one entity serves as a foundational, self-sufficient support structure for another, not relying on additional supports or connections.
-
D.
loyaltyAlliance
Indicates a committed, supportive alliance in which one party maintains steadfast loyalty to another.
-
E.
supporterOf
Indicates that one entity backs, advocates for, or provides assistance to another entity, cause, or organization.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65802f57081909e4e94694684bda4 |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.