Triple
T31248940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | שבט שמעון |
E796761
|
entity |
| Predicate | laterAssimilatedInto |
P13314
|
FINISHED |
| Object | שבט יהודה |
—
|
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: שבט יהודה | Statement: [שבט שמעון, laterAssimilatedInto, שבט יהודה]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAssimilatedInto Context triple: [שבט שמעון, laterAssimilatedInto, שבט יהודה]
-
A.
languageOfAssimilation
Indicates the language used to integrate or absorb individuals or groups into a dominant culture or society.
-
B.
culturalAssimilationInto
Indicates a process where one entity adopts or integrates into the cultural norms, values, and practices of another entity or group.
-
C.
laterIncorporatedInto
chosen
Indicates that one entity was subsequently merged into, absorbed by, or formally made part of another entity at a later time.
-
D.
laterAdoptedIn
Indicates that one entity was adopted, implemented, or taken up in another entity at a subsequent time relative to some earlier reference point or context.
-
E.
linguisticAssimilation
Indicates the process by which one language or linguistic feature becomes more similar to or integrated with another through contact or influence.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: April 29, 2026, 9:11 p.m.