Triple
T31810935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Beaugency |
E812003
|
entity |
| Predicate | englishGarrison |
P24784
|
FINISHED |
| Object | English-held Beaugency castle |
—
|
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: English-held Beaugency castle | Statement: [Battle of Beaugency, englishGarrison, English-held Beaugency castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: englishGarrison Context triple: [Battle of Beaugency, englishGarrison, English-held Beaugency castle]
-
A.
garrisonLanguage
Indicates the language used or officially designated for communication within a military garrison.
-
B.
garrisonIncluded
Indicates that a particular garrison is included within, or forms part of, a specified larger military force, unit, or installation.
-
C.
garrisonTown
Indicates that a town serves as a military base or station where armed forces are permanently or regularly housed.
-
D.
garrisonLabel
Indicates the designation or identifying label assigned to a military garrison associated with an entity.
-
E.
garrisonSide
chosen
Indicates the side, faction, or allegiance that a garrison is associated with or belongs to.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:43 p.m.