Triple
T19342381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States frontier army |
E483788
|
entity |
| Predicate | garrisonLocations |
P70155
|
FINISHED |
| Object | frontier forts |
—
|
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: frontier forts | Statement: [United States frontier army, garrisonLocations, frontier forts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonLocations Context triple: [United States frontier army, garrisonLocations, frontier forts]
-
A.
garrisonOrMobilizationPoint
chosen
Indicates a location where military forces are stationed, assembled, or prepared for deployment or mobilization.
-
B.
garrisonOrigin
Indicates that a garrison or stationed military force originates from, or was initially formed in, a specified location or source.
-
C.
garrisonTown
Indicates that a town serves as a military base or station where armed forces are permanently or regularly housed.
-
D.
garrisonRegion
Indicates that a military force is stationed in and responsible for defending a specific region.
-
E.
garrisonOrRecruitmentArea
Indicates an area designated for stationing military forces or for recruiting personnel into those 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185795bc8190a63061ca794c0d67 |
completed | April 20, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:33 p.m.