Triple

T10275275
Position Surface form Disambiguated ID Type / Status
Subject Labná E240948 entity
Predicate hasStructure P35 FINISHED
Object Labná arch E240948 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: Labná arch | Statement: [Labná, hasStructure, Labná arch]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Labná arch
Context triple: [Labná, hasStructure, Labná arch]
  • A. Labná chosen
    Labná is a small ancient Maya archaeological site in Mexico’s Yucatán Peninsula, noted for its ornate Puuc-style architecture and iconic arched gateway.
  • B. Laborec
    Laborec is a river in eastern Slovakia that flows through the Carpathian region and is a tributary of the Latorica River.
  • C. Labro
    Labro is a small medieval hilltop village in central Italy known for its well-preserved historic architecture and scenic views over Lake Piediluco.
  • D. Sloup
    Sloup is a small village in the Czech Republic known as a gateway to the Moravian Karst cave region and its popular karst formations.
  • E. Ráckeve
    Ráckeve is a historic town in central Hungary situated along the Danube River, known for its Serbian cultural heritage and baroque architecture.
  • 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_69d381a94c1881908fc38fc263d9b9c2 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d28b6cd4819084a7a5c1893b5ad8 completed April 7, 2026, 9:46 a.m.
NED1 Entity disambiguation (via context triple) batch_69d6f81b39008190af48de31de03682e completed April 9, 2026, 12:51 a.m.
Created at: April 6, 2026, 11:37 a.m.