Triple

T8794339
Position Surface form Disambiguated ID Type / Status
Subject Oud Ade E209248 entity
Predicate hasOfficialName P66 FINISHED
Object Oud Ade E209248 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: Oud Ade | Statement: [Oud Ade, hasOfficialName, Oud Ade]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oud Ade
Context triple: [Oud Ade, hasOfficialName, Oud Ade]
  • A. Oud Ade chosen
    Oud Ade is a small village in the Dutch province of South Holland, known for its rural character and location amid the lakes and waterways of the Kaag en Braassem area.
  • B. Oud Metha
    Oud Metha is a central residential and commercial district in Dubai known for its schools, cultural clubs, and easy access to major city landmarks.
  • C. Oud
    Oud is a Dutch surname most notably associated with figures such as architect Jacobus Oud and politician Pieter Oud.
  • D. O’dam
    O’dam are an Indigenous people of northern Mexico, traditionally known as Tepehuan, with their own distinct language and cultural practices.
  • E. Sadri
    Sadri is an Indo-Aryan language widely used as a lingua franca among tribal and non-tribal communities in eastern and central India, particularly in Jharkhand, Chhattisgarh, and surrounding regions.
  • 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_69ca836240888190a62b262e56a69d2f completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5f9f0ff48190a8ff3c7447833849 completed March 31, 2026, 11:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf6f532ed48190a21996f865428831 completed April 3, 2026, 7:42 a.m.
Created at: March 30, 2026, 6:43 p.m.