Triple
T38652345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Ardent |
E939790
|
entity |
| Predicate | missionDuringFalklandsWar |
P97151
|
FINISHED |
| Object | naval gunfire support in Falkland Sound |
—
|
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: naval gunfire support in Falkland Sound | Statement: [HMS Ardent, missionDuringFalklandsWar, naval gunfire support in Falkland Sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionDuringFalklandsWar Context triple: [HMS Ardent, missionDuringFalklandsWar, naval gunfire support in Falkland Sound]
-
A.
falklandsWarService
Indicates that an entity served in a military capacity during the Falklands War.
-
B.
falklandsWarIncident
chosen
Indicates an event or occurrence that took place as part of, or in direct connection with, the Falklands War.
-
C.
FalklandsWarBelligerent
Indicates that an entity was a participating belligerent (a warring party) in the Falklands War.
-
D.
FalklandsRole
Indicates that an entity has a specific role, function, or involvement in relation to the Falkland Islands or the Falklands conflict.
-
E.
hasRankAtTimeOfFalklandsWar
Indicates the military rank an individual held specifically during the time of the Falklands War.
- 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:33 p.m.