Triple
T19076017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ophrah of the Abiezrites |
E466903
|
entity |
| Predicate | regionWithinTribe |
P118180
|
FINISHED |
| Object | central highlands of Canaan |
—
|
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: central highlands of Canaan | Statement: [Ophrah of the Abiezrites, regionWithinTribe, central highlands of Canaan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionWithinTribe Context triple: [Ophrah of the Abiezrites, regionWithinTribe, central highlands of Canaan]
-
A.
associatedTribeLocation
chosen
Indicates a relationship where a tribe is linked or connected to a specific geographic location.
-
B.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
C.
tribalRestriction
Indicates a limitation, condition, or rule that applies specifically based on tribal affiliation or tribal status.
-
D.
recognizedTribe
Indicates that a group is officially acknowledged as a tribe by a governing or authoritative body.
-
E.
stateRecognizedTribe
Indicates that a tribe is officially acknowledged and recognized by a state government as a tribal 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e49c7c8190b6ce7b918086b23c |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.