Triple
T27019214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suratgarh |
E680617
|
entity |
| Predicate | hasNearbyMilitaryInstallations |
P34345
|
FINISHED |
| Object | field firing ranges |
—
|
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: field firing ranges | Statement: [Suratgarh, hasNearbyMilitaryInstallations, field firing ranges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyMilitaryInstallations Context triple: [Suratgarh, hasNearbyMilitaryInstallations, field firing ranges]
-
A.
hasFormerMilitaryInstallationNearby
Indicates that an entity is located close to a site where a military installation previously existed but is no longer active.
-
B.
nearMilitaryInstallation
Indicates that one entity is located in close physical proximity to a military installation or facility.
-
C.
hasNearbyMilitaryTrainingArea
chosen
Indicates that an entity is located close to a designated area used for military training activities.
-
D.
isMilitaryInstallation
Indicates that a location functions as a military facility or base used for defense, training, operations, or related armed forces activities.
-
E.
hasMilitaryBase
Indicates that one entity possesses, hosts, or contains a military base associated with or located on another entity.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 27, 2026, 7:07 a.m.