Triple

T19209157
Position Surface form Disambiguated ID Type / Status
Subject Moya E480311 entity
Predicate hasNameInLanguage P15 FINISHED
Object Moya@es NE NERFINISHED

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: Moya@es | Statement: [Moya, hasNameInLanguage, Moya@es]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moya@es
Context triple: [Moya, hasNameInLanguage, Moya@es]
  • A. Moy
    Moy is a small village in County Tyrone, Northern Ireland, known for its historic market square and location near the River Blackwater.
  • B. MOIA
    MOIA is a mobility services company focused on ride-pooling and urban transportation solutions, operating as a subsidiary of the Volkswagen Group.
  • C. Moya chosen
    Moya is a historic Spanish locality traditionally associated with the noble title of the Marquis of Moya.
  • D. Molló
    Molló is a small mountain village in the Catalan Pyrenees of northeastern Spain, known for its scenic landscapes and proximity to the French border.
  • E. Moys
    Moys was a village near Görlitz in present-day Germany, historically notable as the site of the 1757 Battle of Moys during the Seven Years’ War.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8cb8c348190b52075823911c869 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5f9a000188190afb762ea24bc3deb completed April 20, 2026, 10:02 a.m.
Created at: April 10, 2026, 1:20 p.m.