Triple
T24294770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qibla (toward the Kaaba) |
E605927
|
entity |
| Predicate | locatedInReferenceCity |
P85444
|
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: [Qibla (toward the Kaaba), locatedInReferenceCity, Mecca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInReferenceCity Context triple: [Qibla (toward the Kaaba), locatedInReferenceCity, Mecca]
-
A.
basedInCity
Indicates that an entity has its primary location, headquarters, or main operations situated in a specified city.
-
B.
cityOfReference
chosen
Indicates that one entity serves as the primary or official city associated with, or used as a reference point for, another entity.
-
C.
locatedInCityWithSignificance
Indicates that an entity is located in a city that holds particular importance or notable significance (e.g., historical, cultural, political, or economic).
-
D.
refersToCityOn
Indicates that one entity makes reference to, or is specifically about, a particular city located on a given date or temporal context.
-
E.
cityLocatedIn
Indicates that a city is geographically situated within a specified larger administrative or territorial region.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f291593c0881908a6827f0d8899fe6 |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 12:09 a.m.