Triple
T33110935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMS Leipzig |
E847328
|
entity |
| Predicate | yearOfBattleOfTheFalklandIslands |
P107642
|
FINISHED |
| Object | 1914 |
—
|
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: 1914 | Statement: [SMS Leipzig, yearOfBattleOfTheFalklandIslands, 1914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfBattleOfTheFalklandIslands Context triple: [SMS Leipzig, yearOfBattleOfTheFalklandIslands, 1914]
-
A.
resultAtBattleOfTheFalklandIslands
Indicates the outcome or consequence that occurred specifically in the Battle of the Falkland Islands.
-
B.
FalklandsWarBelligerent
Indicates that an entity was a participating belligerent (a warring party) in the Falklands War.
-
C.
dateOfEngagementAtFalklandIslands
chosen
Indicates the date on which an engagement (such as a battle, conflict, or significant encounter) took place at the Falkland Islands.
-
D.
falklandsWarService
Indicates that an entity served in a military capacity during the Falklands War.
-
E.
resultAtFalklandIslands
Indicates that something has its outcome, effect, or result occurring at or associated with the Falkland Islands.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 1, 2026, 1:27 a.m.