Triple
T4664975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British East India Company forces |
E102823
|
entity |
| Predicate | garrisoned |
P28243
|
FINISHED |
| Object | fortified trading posts |
—
|
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: fortified trading posts | Statement: [British East India Company forces, garrisoned, fortified trading posts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisoned Context triple: [British East India Company forces, garrisoned, fortified trading posts]
-
A.
garrisonedUnit
Indicates that one unit is stationed inside, occupying, or defending another entity such as a building, vehicle, or fortification.
-
B.
garrisonedForce
chosen
Indicates that a military force is stationed in and occupies a specific location, typically for defense or control.
-
C.
garrisonOrAssemblyArea
Indicates a location where military forces are stationed, housed, or gathered for organization, preparation, or deployment.
-
D.
garrisonSide
Indicates the side, faction, or allegiance that a garrison is associated with or belongs to.
-
E.
garrisonSize
Indicates the number of troops or defenders stationed at a particular location as its garrison.
- 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.