Triple
T9298498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Fustian |
E223698
|
entity |
| Predicate | invasionPhase |
P72305
|
FINISHED |
| Object | early phase of Allied invasion of Sicily |
—
|
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: early phase of Allied invasion of Sicily | Statement: [Operation Fustian, invasionPhase, early phase of Allied invasion of Sicily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invasionPhase Context triple: [Operation Fustian, invasionPhase, early phase of Allied invasion of Sicily]
-
A.
warPhase
chosen
Indicates the specific stage or period within a war or armed conflict during which an event, action, or condition occurs.
-
B.
invade
Indicates entering another entity’s territory or domain, typically by force or without permission, in order to take control or exert dominance.
-
C.
missionPhaseAfter
Indicates that one mission phase occurs later in sequence or time than another mission phase.
-
D.
acquisitionPhase
Indicates the stage or phase within an overall acquisition process in which the related entities are currently involved.
-
E.
invasionDate
Indicates the date on which an invasion event occurred or began.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08cf50cc8190a025f478dff4f9fd |
completed | April 1, 2026, noon |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.