Triple
T28517384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokolče, Czechoslovakia |
E721656
|
entity |
| Predicate | countryAtTimeOfSubmergence |
P878
|
FINISHED |
| Object | Czechoslovakia |
—
|
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: Czechoslovakia | Statement: [Sokolče, Czechoslovakia, countryAtTimeOfSubmergence, Czechoslovakia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryAtTimeOfSubmergence Context triple: [Sokolče, Czechoslovakia, countryAtTimeOfSubmergence, Czechoslovakia]
-
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.
hasShipwrecksFrom
Indicates that something contains or is associated with shipwrecks originating from a specified source, location, or time period.
-
C.
coastalCountryAtTheTime
Indicates that a country had a coastline (i.e., bordered a sea or ocean) during a specified time period.
-
D.
countryOfShipSunk
Indicates the country to which a ship that was sunk belonged or was registered.
-
E.
countryAtTheTime
chosen
Indicates that an entity is associated with a specific country as it existed at a particular point in time.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: April 28, 2026, 3:18 a.m.