Triple
T25410857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinana tribe |
E636690
|
entity |
| Predicate | locatedNear (historical heartland) |
P133903
|
FINISHED |
| Object | Hijaz |
—
|
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: Hijaz | Statement: [Kinana tribe, locatedNear (historical heartland), Hijaz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedNear (historical heartland) Context triple: [Kinana tribe, locatedNear (historical heartland), Hijaz]
-
A.
locatedInOrNearModernSettlement
Indicates that something is situated within or in close proximity to a present-day town, city, or other populated settlement.
-
B.
historicallyLocatedNear
chosen
Indicates that, in a historical context, one entity was geographically situated close to another entity.
-
C.
hasHistoricCenterNearby
Indicates that one entity is located close to another entity that serves as a historic center or historically significant core area.
-
D.
foundedNear
Indicates that one entity established or created another entity at a location geographically close to a specified reference entity or place.
-
E.
hasNearbyHistoricArea
Indicates that one entity is located close to another entity that is designated as a historic area.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 21, 2026, 1:53 p.m.