Triple
T25410858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinana tribe |
E636690
|
entity |
| Predicate | locatedNear (historical presence) |
P133903
|
FINISHED |
| Object | Mecca |
—
|
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: Mecca | Statement: [Kinana tribe, locatedNear (historical presence), Mecca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedNear (historical presence) Context triple: [Kinana tribe, locatedNear (historical presence), Mecca]
-
A.
historicallyLocatedNear
chosen
Indicates that, in a historical context, one entity was geographically situated close to another entity.
-
B.
locatedInOrNearModernSettlement
Indicates that something is situated within or in close proximity to a present-day town, city, or other populated settlement.
-
C.
historicalLocationOf
Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
-
D.
hasNearbyHistoricArea
Indicates that one entity is located close to another entity that is designated as a historic area.
-
E.
locatedNearFormer
Indicates that one entity is situated close to another entity that previously occupied a nearby or the same location.
- 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_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 21, 2026, 1:53 p.m.