Triple
T36196869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle between USS Constitution and HMS Java |
E1047150
|
entity |
| Predicate | shipSurrendered |
P29098
|
FINISHED |
| Object | HMS Java |
—
|
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: HMS Java | Statement: [Battle between USS Constitution and HMS Java, shipSurrendered, HMS Java]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipSurrendered Context triple: [Battle between USS Constitution and HMS Java, shipSurrendered, HMS Java]
-
A.
shipSankIn
Indicates that a specific ship sank (was lost or submerged) in a particular location or body of water.
-
B.
shipLostWith
Indicates that one entity was lost together with another entity in the same maritime incident or disappearance.
-
C.
sankWhile
Indicates that one entity moved downward below a surface or level at the same time that another specified event or action was occurring.
-
D.
surrenderedIn
chosen
Indicates that an entity yielded or gave up control, power, or resistance within a specific event, context, or situation.
-
E.
sankOn
Indicates that one entity moved downward and became submerged or lower in level relative to another entity or reference point.
- 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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.