Triple
T6588287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribe of Zebulun |
E159281
|
entity |
| Predicate | statusAfterExile |
P71651
|
FINISHED |
| Object | lost tribe |
—
|
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: lost tribe | Statement: [Tribe of Zebulun, statusAfterExile, lost tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterExile Context triple: [Tribe of Zebulun, statusAfterExile, lost tribe]
-
A.
wasExiled
Indicates that an entity was forcibly sent away from their home or country, typically as a punishment or due to political or social pressures.
-
B.
periodOfExile
Indicates a time span during which an entity is banished, expelled, or forced to live away from its native or rightful place.
-
C.
legalStatusAfterEscape
Indicates the legal status or condition assigned to an individual after they have escaped from custody, confinement, or lawful control.
-
D.
traditionallyExiledTo
Indicates that an entity has, by long-standing custom or tradition, been sent away or banished to a particular place.
-
E.
hasPreviousExile
Indicates that an entity has experienced at least one prior period of exile before the current or referenced state.
- F. None of above. chosen
Provenance (4 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_69c688366ce8819083f8883983c0df92 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6c07bb434819096ec3e3b966042a5 |
completed | March 27, 2026, 5:38 p.m. |
Created at: March 27, 2026, 1:55 p.m.