Triple

T20259097
Position Surface form Disambiguated ID Type / Status
Subject Derwent (submerged village) E498781 entity
Predicate populationAfterSubmergence P84294 FINISHED
Object 0 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: 0 | Statement: [Derwent (submerged village), populationAfterSubmergence, 0]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: populationAfterSubmergence
Context triple: [Derwent (submerged village), populationAfterSubmergence, 0]
  • A. populationAfterDestruction chosen
    Indicates the size or composition of a population following an event of destruction or devastation.
  • B. impactOfSubmergence
    Indicates the effect or consequences that submerging one entity (typically in a fluid or environment) has on another entity or on its properties.
  • C. hasCauseOfSubmergence
    Indicates a relationship where one entity is the cause or reason for another entity becoming submerged or underwater.
  • D. partiallyInundatedSince
    Indicates that an entity has been partially covered or flooded by water starting from a specific point in time and continuing thereafter.
  • E. formedBySubmerging
    Indicates that something comes into existence or is created as a result of being placed or held beneath the surface of a liquid.
  • 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_69da6275fa6c8190952924930adee150 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e674c84e848190a6e8956698b84026 completed April 20, 2026, 6:47 p.m.
PD Predicate disambiguation batch_69e55b1b23f88190bdcbe2f81dd226dd completed April 19, 2026, 10:45 p.m.
Created at: April 11, 2026, 11:41 p.m.