Triple
T35571986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | region of Samaria |
E1027965
|
entity |
| Predicate | historicalTribeTerritory |
P199418
|
FINISHED |
| Object | Tribe of Ephraim |
—
|
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: Tribe of Ephraim | Statement: [region of Samaria, historicalTribeTerritory, Tribe of Ephraim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalTribeTerritory Context triple: [region of Samaria, historicalTribeTerritory, Tribe of Ephraim]
-
A.
territoryAtTime
Indicates that a specified territory is associated with or held by an entity during a particular time or time interval.
-
B.
historicTerritoryLocation
chosen
Indicates that one entity is the geographical area where another entity historically held territory or exercised territorial control.
-
C.
historicalTerritoryType
Indicates that a territory is classified according to a specific type or category it held during a historical period.
-
D.
historicalRegionOfInfluence
Indicates that one entity was historically within the geographic, political, or cultural sphere of influence of another entity.
-
E.
historicalTerritoryOverlap
Indicates that two entities have had overlapping territorial boundaries during some period in their historical existence.
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00b479c1588190af6e0698b7f8d7f7 |
completed | May 10, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_6a00b4158260819087d0cfad8b18cef4 |
completed | May 10, 2026, 4:36 p.m. |
Created at: May 3, 2026, 4:04 p.m.