Triple
T37871757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gagra |
E944622
|
entity |
| Predicate | locatedInFederalIslamicRepublic |
P204436
|
FINISHED |
| Object | Pakistan |
E1646
|
NE 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: Pakistan | Statement: [Gagra, locatedInFederalIslamicRepublic, Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInFederalIslamicRepublic Context triple: [Gagra, locatedInFederalIslamicRepublic, Pakistan]
-
A.
locatedInTheCountryGoverned
Indicates that one entity is situated within the geographical boundaries of a country that is governed or administered by another specified entity.
-
B.
locatedInFederalEntity
Indicates that one entity is geographically or administratively situated within the jurisdiction or boundaries of a specified federal entity.
-
C.
politicallyLocatedIn
Indicates that an entity is situated within or belongs to a particular political or administrative jurisdiction or territory.
-
D.
locatedInCapital
Indicates that an entity is situated within the capital city of a specified region, country, or administrative area.
-
E.
isLocatedOn
Indicates that one entity exists at or is situated upon the surface or area of another entity.
- F. None of above. chosen
Provenance (5 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a410cbcc87481908e6e344d8fd32a63 |
completed | June 28, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:19 p.m.