Triple
T19141724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeredah |
E468574
|
entity |
| Predicate | traditionallyIdentifiedIn |
P43083
|
FINISHED |
| Object | territory 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: territory of Ephraim | Statement: [Zeredah, traditionallyIdentifiedIn, territory of Ephraim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyIdentifiedIn Context triple: [Zeredah, traditionallyIdentifiedIn, territory of Ephraim]
-
A.
isTraditionallyIdentifiedAs
chosen
Indicates that one entity is customarily or historically recognized or labeled as being the same as, or corresponding to, another entity.
-
B.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
-
C.
traditionallyFoundIn
Indicates that something is customarily or historically located, used, or present within a particular place, context, or setting.
-
D.
countryOfNamingTradition
Indicates the country whose cultural or linguistic naming conventions are used to form or interpret a given name.
-
E.
hasLocationTraditionallyIdentifiedAs
Indicates that something is situated in, or associated with, a place that is customarily or historically recognized as its location, even if this identification is not formally verified.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e975e09c8190911e98e6e558615d |
completed | April 20, 2026, 8:53 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.