Triple
T19705173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Gibraltar (1727) |
E473194
|
entity |
| Predicate | garrisonStrengthDefenders |
P13142
|
FINISHED |
| Object | approximately 5,000 men |
—
|
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: approximately 5,000 men | Statement: [Siege of Gibraltar (1727), garrisonStrengthDefenders, approximately 5,000 men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonStrengthDefenders Context triple: [Siege of Gibraltar (1727), garrisonStrengthDefenders, approximately 5,000 men]
-
A.
garrisonSize
chosen
Indicates the number of troops or defenders stationed at a particular location as its garrison.
-
B.
garrisonDuringBattle
Indicates that an entity is stationed to defend or hold a location specifically during the time a battle is taking place.
-
C.
garrisonDuringWar
Indicates that a military force is stationed in a specific location for defense or control during a time of war.
-
D.
garrisonMaintainedBy
Indicates that a military garrison is operated, supported, or kept in readiness by a specified controlling entity.
-
E.
garrisonTown
Indicates that a town serves as a military base or station where armed forces are permanently or regularly housed.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b998608190a82f23bbf77f7bd2 |
completed | April 20, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.