Triple
T31746157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umballa |
E810274
|
entity |
| Predicate | presentDayUrbanSuccessor |
P138593
|
FINISHED |
| Object | Ambala Cantonment |
—
|
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: Ambala Cantonment | Statement: [Umballa, presentDayUrbanSuccessor, Ambala Cantonment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayUrbanSuccessor Context triple: [Umballa, presentDayUrbanSuccessor, Ambala Cantonment]
-
A.
present-daySuccessor
Indicates that one entity is the current-day successor or continuation of another entity (e.g., an institution, organization, or administrative unit).
-
B.
presentDayCityIs
chosen
Indicates that one entity is the current, modern-day city corresponding to or located at the place represented by the other entity.
-
C.
presentDayNear
Indicates that one entity is located a short distance from another in the present time or current context.
-
D.
successorInCity
Indicates that one entity directly follows or replaces another in holding a particular role, position, or function within the same city.
-
E.
presentDayRemains
Indicates that something from the past still exists or has surviving traces in the present day.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 30, 2026, 11:26 p.m.