Triple
T37845568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Fort St. Philip |
E943589
|
entity |
| Predicate | hasGarrisonStrength |
P87717
|
FINISHED |
| Object | approximately 2800 British troops |
—
|
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 2800 British troops | Statement: [Siege of Fort St. Philip, hasGarrisonStrength, approximately 2800 British troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGarrisonStrength Context triple: [Siege of Fort St. Philip, hasGarrisonStrength, approximately 2800 British troops]
-
A.
hasGarrisonOutpostChoice
Indicates that an entity is associated with a selectable option regarding the placement or use of a garrison outpost.
-
B.
garrisonSize
Indicates the number of troops or defenders stationed at a particular location as its garrison.
-
C.
hasApproximateDefendingForceSize
chosen
Indicates that an entity is associated with a defending force whose size is known only approximately rather than as an exact value.
-
D.
garrisonIncluded
Indicates that a particular garrison is included within, or forms part of, a specified larger military force, unit, or installation.
-
E.
garrisonMaintainedBy
Indicates that a military garrison is operated, supported, or kept in readiness by a specified controlling 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:19 p.m.