Triple
T4000569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribe of Simeon |
E89403
|
entity |
| Predicate | allottedTerritoryIn |
P22232
|
FINISHED |
| Object | southern part of ancient 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: southern part of ancient Israel | Statement: [Tribe of Simeon, allottedTerritoryIn, southern part of ancient Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allottedTerritoryIn Context triple: [Tribe of Simeon, allottedTerritoryIn, southern part of ancient Israel]
-
A.
distributorTerritory
Indicates the geographic area or market in which a distributor is authorized or responsible to sell or distribute products or services.
-
B.
activeInTerritory
Indicates that an entity conducts operations, activities, or maintains a presence within a specified geographic territory.
-
C.
territoryIncluded
Indicates that one territory is geographically or administratively contained within another territory.
-
D.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
E.
receivedTerritory
chosen
Indicates that one entity was granted or took possession of a territory from another 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa8579288190940487ad07e38de0 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8f89f2881909b0965419d15d46c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.