Triple

T9319642
Position Surface form Disambiguated ID Type / Status
Subject Goudswaard E224212 entity
Predicate locatedNear P294 FINISHED
Object Piershil E353559 NE 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: Piershil | Statement: [Goudswaard, locatedNear, Piershil]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Piershil
Context triple: [Goudswaard, locatedNear, Piershil]
  • A. Piershil chosen
    Piershil is a small village in the Dutch province of South Holland, known for its rural character and location on the island of Hoeksche Waard.
  • B. Polyanka
    Polyanka is a Moscow Metro station on the Serpukhovsko–Timiryazevskaya Line, located near the city center and serving the surrounding Polyanka Street area.
  • C. Garia
    Garia is a traditional tribal deity venerated in parts of Northeast India, particularly among the Tripuri people, as a god associated with prosperity, fertility, and protection.
  • D. Bronnitsy
    Bronnitsy is a historic town in Russia known for its jewelry-making traditions and its location southeast of Moscow along the Moskva River.
  • E. Oreshek
    Oreshek is the historic Russian fortress on Lake Ladoga that later gave rise to the town of Shlisselburg.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca8426d48481909596360f7791c7dd completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd358c7d348190a10fd8670d7756f5 completed April 1, 2026, 3:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69d0c7cc71e48190afdc3f1120ce5e02 completed April 4, 2026, 8:11 a.m.
Created at: March 30, 2026, 7:38 p.m.