Triple
T4812365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Louisbourg (1758) |
E107100
|
entity |
| Predicate | garrisonSurrendered |
P29098
|
FINISHED |
| Object | French garrison of Louisbourg |
—
|
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: French garrison of Louisbourg | Statement: [Siege of Louisbourg (1758), garrisonSurrendered, French garrison of Louisbourg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonSurrendered Context triple: [Siege of Louisbourg (1758), garrisonSurrendered, French garrison of Louisbourg]
-
A.
placeOfSurrender
Indicates the location where an entity formally surrendered to another party.
-
B.
surrenderedIn
chosen
Indicates that an entity yielded or gave up control, power, or resistance within a specific event, context, or situation.
-
C.
garrisonAttacked
Indicates that a military garrison was subjected to an attack by another force or entity.
-
D.
surrenderedAfter
Indicates that one entity surrendered following or as a consequence of another specified event, action, or time.
-
E.
laterGarrisonedBy
Indicates that a location or structure was subsequently occupied and used as a military garrison by a specified force or group.
- 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_69bd43f779448190b92885cb70abb6c2 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1dfa3481909d240d50ed0ee38c |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:23 p.m.