Triple

T6076700
Position Surface form Disambiguated ID Type / Status
Subject Maipo Province E135418 entity
Predicate capital P234 FINISHED
Object San Bernardo E145222 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: San Bernardo | Statement: [Maipo Province, capital, San Bernardo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: San Bernardo
Context triple: [Maipo Province, capital, San Bernardo]
  • A. San Bernardo chosen
    San Bernardo is a commune and city in Chile that forms part of the Greater Santiago urban area and serves as an important residential and industrial hub.
  • B. San Bernardo
    San Bernardo is a major transport hub and metro station in Seville, Spain, serving as an interchange between urban rail, tram, and bus services.
  • C. St Bernard
    The St Bernard is a large, gentle Swiss working dog breed historically famed for rescuing travelers in the Alps.
  • D. San Bernardinian
    San Bernardinian refers to a resident or native of San Bernardino, a city in Southern California, United States.
  • E. Canino
    Canino is a small town in the Lazio region of central Italy, historically notable as the birthplace of Pope Paul III.
  • 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_69c0087ad31c8190ab936e0ff28614b6 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c0576ef2c88190b0ec62e9f041d176 completed March 22, 2026, 8:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69c11d43f7908190845c2337cd243a3c completed March 23, 2026, 11 a.m.
Created at: March 22, 2026, 4:11 p.m.