Triple
T6768082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambala Air Force Station |
E154772
|
entity |
| Predicate | nearbyCity |
P350
|
FINISHED |
| Object | Ambala Cantonment |
E449635
|
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: Ambala Cantonment | Statement: [Ambala Air Force Station, nearbyCity, Ambala Cantonment]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ambala Cantonment Context triple: [Ambala Air Force Station, nearbyCity, Ambala Cantonment]
-
A.
Ambala Cantonment
chosen
Ambala Cantonment is a prominent military and commercial town in Haryana, India, known for its strategic location and major railway junction.
-
B.
Jhelum Cantonment
Jhelum Cantonment is a major Pakistani military garrison located near the city of Jhelum in Punjab Province.
-
C.
Agra Cantonment
Agra Cantonment is a major Indian Army military station and the primary railway hub of Agra, Uttar Pradesh.
-
D.
Delhi Cantonment
Delhi Cantonment is a prominent military area in New Delhi that serves as a major base and administrative center for the Indian Armed Forces.
-
E.
Jabalpur Cantonment
Jabalpur Cantonment is a major Indian Army cantonment area located in the city of Jabalpur in central India.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c688109c1c8190added9a221292af0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d231b79c81908a4f7fa8f253706d |
completed | March 27, 2026, 6:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c712c150088190b7e827cb1e45f1df |
completed | March 27, 2026, 11:29 p.m. |
Created at: March 27, 2026, 2:12 p.m.