Triple

T9638113
Position Surface form Disambiguated ID Type / Status
Subject River Ouse E232986 entity
Predicate flowsThrough P225 FINISHED
Object Goole E34428 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: Goole | Statement: [River Ouse, flowsThrough, Goole]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Goole
Context triple: [River Ouse, flowsThrough, Goole]
  • A. Goole chosen
    Goole is an inland port town in the East Riding of Yorkshire, England, known for its significant docks and role in regional maritime trade.
  • B. Google
    Google is a multinational technology company best known for its search engine and wide range of internet-related products and services, including Android, YouTube, and cloud computing.
  • C. OGLE
    OGLE (Optical Gravitational Lensing Experiment) is a long-term astronomical survey focused on detecting dark matter, exoplanets, and variable stars through gravitational microlensing and photometric monitoring.
  • D. Bing
    Bing is Microsoft's web search engine that provides internet search, image, video, and mapping services.
  • E. Baidu
    Baidu is a leading Chinese technology company best known for its dominant search engine and extensive work in artificial intelligence.
  • 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_69ca848a5a908190aad251f4137b0c3a completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9b51b08081908e30744607b28953 completed April 1, 2026, 10:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69d18243cfdc81908ecdf039c38de478 completed April 4, 2026, 9:27 p.m.
Created at: March 30, 2026, 8:11 p.m.