Triple

T19826332
Position Surface form Disambiguated ID Type / Status
Subject Loboc Church E476334 entity
Predicate locatedIn P40 FINISHED
Object Loboc 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: Loboc | Statement: [Loboc Church, locatedIn, Loboc]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Loboc
Context triple: [Loboc Church, locatedIn, Loboc]
  • A. Loboc chosen
    Loboc is a riverside town on the Philippine island of Bohol known for its scenic river cruises, historic church, and cultural music traditions.
  • B. Ségny
    Ségny is a small commune in eastern France’s Ain department, situated near the Swiss border in the Auvergne-Rhône-Alpes region.
  • C. Hármas-Körös
    Hármas-Körös is a major branch of the Körös River in southeastern Hungary, formed by the confluence of its tributaries and known for its role in regional water management and recreation.
  • D. Gyöngyös-patak
    Gyöngyös-patak is a small stream in northern Hungary that serves as a tributary of the Zagyva River, flowing through the town of Gyöngyös and its surrounding area.
  • E. Kapós River
    The Kapós River is a watercourse in southwestern Hungary that flows through the Transdanubian region before joining the Sió River.
  • 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_69d8e51c7c188190b926f3a2a7b5f881 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e656c9e7348190a569a40bd1fca6ba completed April 20, 2026, 4:39 p.m.
Created at: April 10, 2026, 1:50 p.m.