Triple

T11893709
Position Surface form Disambiguated ID Type / Status
Subject Interlagos E282981 entity
Predicate hasCorner P42380 FINISHED
Object Ferradura E953584 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: Ferradura | Statement: [Interlagos, hasCorner, Ferradura]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ferradura
Context triple: [Interlagos, hasCorner, Ferradura]
  • A. Ferradura chosen
    Ferradura is a notable high-speed corner at Brazil’s Autódromo José Carlos Pace (Interlagos), challenging drivers with its sweeping, downhill right-hand bend.
  • B. Lazo
    Lazo is a nearby settlement in Primorsky Krai, Russia, known for its proximity to the Lazovsky Nature Reserve on the Sea of Japan coast.
  • C. Tambor
    Tambor is a surname most notably associated with American actor Jeffrey Tambor, known for his roles in television and film.
  • D. Bota
    Bota is a small riverside settlement in the Malaysian state of Perak, situated along the Perak River.
  • E. Plateros
    Plateros is a major Catholic pilgrimage site in Zacatecas, Mexico, renowned for its sanctuary dedicated to the Santo Niño de Atocha.
  • 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_69d6ab2a90b08190a4e818821cc93e6d completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8dd1172988190a2c13d37220f2f93 completed April 10, 2026, 11:20 a.m.
NED1 Entity disambiguation (via context triple) batch_69f43fe43c7c8190a85d464fd48e00d9 completed May 1, 2026, 5:53 a.m.
Created at: April 8, 2026, 9:44 p.m.