Triple
T32447906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Siege of Ciudad Rodrigo (1810) |
E829195
|
entity |
| Predicate | hasGarrisonSide |
P24784
|
FINISHED |
| Object | Anglo-Spanish garrison |
—
|
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: Anglo-Spanish garrison | Statement: [First Siege of Ciudad Rodrigo (1810), hasGarrisonSide, Anglo-Spanish garrison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGarrisonSide Context triple: [First Siege of Ciudad Rodrigo (1810), hasGarrisonSide, Anglo-Spanish garrison]
-
A.
garrisonSide
chosen
Indicates the side, faction, or allegiance that a garrison is associated with or belongs to.
-
B.
garrisonType
Indicates the specific kind or classification of military garrison associated with an entity.
-
C.
garrisonIncluded
Indicates that a particular garrison is included within, or forms part of, a specified larger military force, unit, or installation.
-
D.
garrisonedUnit
Indicates that one unit is stationed inside, occupying, or defending another entity such as a building, vehicle, or fortification.
-
E.
garrisonOrHQ
Indicates that an entity serves as a military garrison or headquarters location for another entity.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2e767bc8190b49fd0c4a557b464 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:56 a.m.