Triple
T38108955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mangho Pir |
E951601
|
entity |
| Predicate | locatedShrineIn |
P193903
|
FINISHED |
| Object | northwestern Karachi |
—
|
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: northwestern Karachi | Statement: [Mangho Pir, locatedShrineIn, northwestern Karachi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedShrineIn Context triple: [Mangho Pir, locatedShrineIn, northwestern Karachi]
-
A.
possibleShrineLocation
Indicates that a location is suitable or designated as a potential site where a shrine could be placed or constructed.
-
B.
placeOfShrine
chosen
Indicates the location where a shrine is situated or established.
-
C.
hasNearbyShrine
Indicates that one entity is located close to or in the vicinity of a shrine associated with another entity.
-
D.
containsShrine
Indicates that one entity includes or has within its boundaries a shrine associated with it.
-
E.
majorShrineLocation
Indicates that a major religious shrine is located at or associated with a particular place or geographic 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.