Triple
T31746150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umballa |
E810274
|
entity |
| Predicate | hadCantonmentBarracks |
P172902
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Umballa, hadCantonmentBarracks, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCantonmentBarracks Context triple: [Umballa, hadCantonmentBarracks, true]
-
A.
establishedAsCantonmentBy
Indicates that an entity was designated or set up as a cantonment by a specified agent or authority.
-
B.
wasMilitaryHeadquartersOf
Indicates that a place or facility served as the main command center or headquarters for a specific military force or organization.
-
C.
garrisonedDuring
Indicates that a military force was stationed or quartered at a location for defense or control during a specified time period.
-
D.
garrisonOrTheater
Indicates that one entity serves as a military garrison or theater of operations for another entity.
-
E.
garrisonOrAssemblyArea
Indicates a location where military forces are stationed, housed, or gathered for organization, preparation, or deployment.
- F. None of above. chosen
Provenance (4 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_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 30, 2026, 11:26 p.m.