Triple
T23934935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land of Zebulun |
E602606
|
entity |
| Predicate | biblicalTribeCountContext |
P87056
|
FINISHED |
| Object | one of twelve 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: one of twelve tribes of Israel | Statement: [Land of Zebulun, biblicalTribeCountContext, one of twelve tribes of Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biblicalTribeCountContext Context triple: [Land of Zebulun, biblicalTribeCountContext, one of twelve tribes of Israel]
-
A.
numberOfTribes
chosen
Indicates the total count of distinct tribes associated with a given entity or context.
-
B.
membersPerTribe
Indicates the number of individual members associated with each tribe in the relationship.
-
C.
tribeOrGens
Indicates a relationship where an entity belongs to, is associated with, or is identified as a particular tribe or gens (clan/lineage group).
-
D.
tribeCharacterization
Indicates how a tribe or tribal group is characterized or described in terms of its defining qualities, attributes, or identity.
-
E.
hasTribalCitizens
Indicates that one or more individuals are recognized as official members or citizens of a particular tribe.
- 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1cf9e8abc8190a3028a358265912e |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9 p.m.