Triple
T27062901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VII Corps (Grande Armée) |
E685090
|
entity |
| Predicate | garrisonOrTheater |
P161808
|
FINISHED |
| Object | Iberian Peninsula |
—
|
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: Iberian Peninsula | Statement: [VII Corps (Grande Armée), garrisonOrTheater, Iberian Peninsula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonOrTheater Context triple: [VII Corps (Grande Armée), garrisonOrTheater, Iberian Peninsula]
-
A.
garrisonOrTheater
chosen
Indicates that one entity serves as a military garrison or theater of operations for another entity.
-
B.
garrisonOrHQ
Indicates that an entity serves as a military garrison or headquarters location for another entity.
-
C.
garrisonOrAssemblyArea
Indicates a location where military forces are stationed, housed, or gathered for organization, preparation, or deployment.
-
D.
garrisonOrMobilizationPoint
Indicates a location where military forces are stationed, assembled, or prepared for deployment or mobilization.
-
E.
garrisonIncluded
Indicates that a particular garrison is included within, or forms part of, a specified larger military force, unit, or installation.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f622e5c8e4819090baecc212ac8a21 |
completed | May 2, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 8:22 a.m.