Triple
T26748195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RMS Lancastria |
E674459
|
entity |
| Predicate | sunkInCountry |
P86676
|
FINISHED |
| Object | France |
—
|
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: France | Statement: [RMS Lancastria, sunkInCountry, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sunkInCountry Context triple: [RMS Lancastria, sunkInCountry, France]
-
A.
sunkCountry
Indicates that one entity (typically a vessel or force) caused the sinking of a country’s ship(s) or naval assets belonging to another country.
-
B.
sunkBy
Indicates that one entity (typically a vessel or structure) was caused to sink or be destroyed in water by another entity.
-
C.
sunkInBodyOfWater
Indicates that an object or entity has gone beneath the surface and come to rest within a body of water.
-
D.
sunkDuring
Indicates that one entity was sunk in the course of, or as a result of, the event or time period represented by another entity.
-
E.
sunkOff
chosen
Indicates that one entity was sunk at a location situated off (near but not directly at) another referenced place or feature.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61886fd78819096f521fd8b9b1092 |
completed | May 2, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:52 a.m.