Triple
T2542730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Drogheda |
E57820
|
entity |
| Predicate | hasGarrisonStrengthApprox |
P13142
|
FINISHED |
| Object | about 2,500 to 3,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: about 2,500 to 3,000 men | Statement: [Siege of Drogheda, hasGarrisonStrengthApprox, about 2,500 to 3,000 men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGarrisonStrengthApprox Context triple: [Siege of Drogheda, hasGarrisonStrengthApprox, about 2,500 to 3,000 men]
-
A.
garrisonSize
chosen
Indicates the number of troops or defenders stationed at a particular location as its garrison.
-
B.
garrisonedUnit
Indicates that one unit is stationed inside, occupying, or defending another entity such as a building, vehicle, or fortification.
-
C.
garrisonOrHQ
Indicates that an entity serves as a military garrison or headquarters location for another entity.
-
D.
garrisonedForce
Indicates that a military force is stationed in and occupies a specific location, typically for defense or control.
-
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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2bf6cac819083a9ab9d041d8641 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.