Triple
T24695697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yakutsk Ostrog |
E611576
|
entity |
| Predicate | militaryGarrison |
P28243
|
FINISHED |
| Object | Cossacks |
—
|
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: Cossacks | Statement: [Yakutsk Ostrog, militaryGarrison, Cossacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryGarrison Context triple: [Yakutsk Ostrog, militaryGarrison, Cossacks]
-
A.
garrisonedForce
chosen
Indicates that a military force is stationed in and occupies a specific location, typically for defense or control.
-
B.
garrisonOrMobilizationPoint
Indicates a location where military forces are stationed, assembled, or prepared for deployment or mobilization.
-
C.
garrisonedUnit
Indicates that one unit is stationed inside, occupying, or defending another entity such as a building, vehicle, or fortification.
-
D.
garrisonOrAssemblyArea
Indicates a location where military forces are stationed, housed, or gathered for organization, preparation, or deployment.
-
E.
garrisonFunction
Indicates that an entity serves as a military garrison or base for another entity, providing housing, support, or operational facilities for its forces.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:21 a.m.