Triple
T11087672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Glasgow (D88) |
E262163
|
entity |
| Predicate | falklandsWarRole |
P42949
|
FINISHED |
| Object | provided area air defence |
—
|
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: provided area air defence | Statement: [HMS Glasgow (D88), falklandsWarRole, provided area air defence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: falklandsWarRole Context triple: [HMS Glasgow (D88), falklandsWarRole, provided area air defence]
-
A.
FalklandsWarBelligerent
Indicates that an entity was a participating belligerent (a warring party) in the Falklands War.
-
B.
combatantRoleOfUnitedKingdom
chosen
Indicates that the specified combatant role is one that was held by, or associated with, the United Kingdom in a particular conflict or military context.
-
C.
hasRankAtTimeOfFalklandsWar
Indicates the military rank an individual held specifically during the time of the Falklands War.
-
D.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
E.
worldWarIIRole
Indicates the specific role, position, or function an entity had in relation to World War II.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799c5008081908f59612243fa4f7a |
completed | April 9, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.