Triple
T7543144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alsace campaign |
E178329
|
entity |
| Predicate | regionDefendedBy |
P15009
|
FINISHED |
| Object | French forces |
—
|
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 forces | Statement: [Alsace campaign, regionDefendedBy, French forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionDefendedBy Context triple: [Alsace campaign, regionDefendedBy, French forces]
-
A.
defenseArea
Indicates a spatial region or zone that is designated for defensive protection or military/security defense activities.
-
B.
canBeDefendedIn
Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
-
C.
defenderIn
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
-
D.
defenceHandledBy
chosen
Indicates that responsibility for managing or conducting a defence is assigned to or carried out by a particular agent or entity.
-
E.
primaryDefendedCity
Indicates that an entity served as the main or principal city that another entity was responsible for defending.
- 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8762b048190a0b262f9cb3fe1b0 |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:48 p.m.