Triple
T37984013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sinking of SMS Emden |
E947634
|
entity |
| Predicate | victoriousShip |
P189823
|
FINISHED |
| Object | HMAS Sydney |
—
|
NE NERFINISHED |
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: HMAS Sydney | Statement: [sinking of SMS Emden, victoriousShip, HMAS Sydney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victoriousShip Context triple: [sinking of SMS Emden, victoriousShip, HMAS Sydney]
-
A.
isWarshipOf
Indicates that a given warship belongs to, is operated by, or is part of the naval forces of a specified country or organization.
-
B.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
C.
notableVictimShip
Indicates that a ship is recognized as a particularly significant or noteworthy victim in a specific incident or context.
-
D.
capturedShip
Indicates that one party has taken control of another party's ship, typically by force or seizure.
-
E.
boardsShip
Indicates that one entity gets onto or enters a ship as a passenger or crew member.
- F. None of above. chosen
Provenance (4 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc993caa881908c16c3e21efaeef9 |
completed | May 6, 2026, 11:07 p.m. |
Created at: May 3, 2026, 4:20 p.m.