Triple
T2966998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shechem |
E80189
|
entity |
| Predicate | tribalTerritory |
P10500
|
FINISHED |
| Object | tribe of Ephraim |
—
|
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: tribe of Ephraim | Statement: [Shechem, tribalTerritory, tribe of Ephraim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribalTerritory Context triple: [Shechem, tribalTerritory, tribe of Ephraim]
-
A.
indigenousTerritoryOf
Indicates that a geographic area is traditionally inhabited, used, or claimed by a particular Indigenous people or community as their ancestral territory.
-
B.
tribalOrganization
Indicates that an entity is organized as, or formally recognized as, a tribal governing or social structure.
-
C.
traditionalTerritorialDesignation
chosen
Indicates a historically or culturally recognized claim or assignment of a geographic area to a particular group, authority, or identity.
-
D.
governingTribalPresence
Indicates that an entity holds governing authority or administrative control over a tribal presence in a given area or context.
-
E.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad996e93788190ba9883714d4dfa0c |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.