Triple
T4761198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levite of Ephraim |
E105701
|
entity |
| Predicate | residenceRegion |
P14194
|
FINISHED |
| Object | hill country 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: hill country of Ephraim | Statement: [Levite of Ephraim, residenceRegion, hill country of Ephraim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residenceRegion Context triple: [Levite of Ephraim, residenceRegion, hill country of Ephraim]
-
A.
traditionalRegionOfResidence
chosen
Indicates the customary or historically established geographic region where an entity (typically a person or group) resides or is considered to be from.
-
B.
homeCityRegion
Indicates the city or broader regional area that serves as an entity’s primary place of residence or origin.
-
C.
residencyLocation
Indicates the place where an entity lives or maintains its primary residence.
-
D.
recipientRegion
Indicates the geographic region that receives or is the destination of a transfer, delivery, or directed action.
-
E.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650eefe08190b99f9f01b121dbfd |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.