Triple
T25352219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribes of Israel |
E635716
|
entity |
| Predicate | laterUnifiedUnder |
P49874
|
FINISHED |
| Object | King Saul |
—
|
NE NERFINISHED |
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: King Saul | Statement: [Tribes of Israel, laterUnifiedUnder, King Saul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterUnifiedUnder Context triple: [Tribes of Israel, laterUnifiedUnder, King Saul]
-
A.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
B.
historicalPeriodOfUnification
Indicates the historical time span during which separate entities were unified into a single political or organizational whole.
-
C.
unificationLedTo
Indicates that a process of unifying previously separate entities resulted in or caused a particular outcome or state.
-
D.
aimedToUnify
Indicates an intention or effort by one entity to bring multiple entities, groups, or elements together into a single unified whole.
-
E.
consolidatedUnder
chosen
Indicates that one entity has been merged into and is now formally part of another, typically larger or parent, entity.
- 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 21, 2026, 1:34 p.m.