Triple
T19851936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Micah |
E477016
|
entity |
| Predicate | locatedInTextualRegion |
P134241
|
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: [House of Micah, locatedInTextualRegion, hill country of Ephraim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTextualRegion Context triple: [House of Micah, locatedInTextualRegion, hill country of Ephraim]
-
A.
locatedInTextualSource
chosen
Indicates that information about an entity or relation appears within, or is documented by, a specific textual source.
-
B.
locatedInArticle
Indicates that one item (such as a section, figure, or concept) appears within or is contained in a specific article.
-
C.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
regionRuledLocatedIn
Indicates that the region governed or ruled by an entity is geographically located within a specified larger area or place.
-
E.
locationInDocument
Indicates that one entity specifies where another entity is situated or referenced within a document.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65869e1b481908e2a2a2074ff4a6d |
completed | April 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.