Triple
T19976006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashopton |
E493691
|
entity |
| Predicate | fullySubmergedByYear |
P42186
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [Ashopton, fullySubmergedByYear, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullySubmergedByYear Context triple: [Ashopton, fullySubmergedByYear, 1945]
-
A.
hasCauseOfSubmergence
Indicates a relationship where one entity is the cause or reason for another entity becoming submerged or underwater.
-
B.
submergedBy
chosen
Indicates that one entity is covered or overwhelmed by liquid, typically water, to the point of being beneath its surface due to the action or presence of another entity.
-
C.
formedBySubmerging
Indicates that something comes into existence or is created as a result of being placed or held beneath the surface of a liquid.
-
D.
impactOfSubmergence
Indicates the effect or consequences that submerging one entity (typically in a fluid or environment) has on another entity or on its properties.
-
E.
partiallyInundatedSince
Indicates that an entity has been partially covered or flooded by water starting from a specific point in time and continuing thereafter.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d0f4fb48190ad63afeff3513523 |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:26 p.m.