Triple

T24472510
Position Surface form Disambiguated ID Type / Status
Subject La Paz batchoy E617138 entity
Predicate traditionallySoldAt P15059 FINISHED
Object La Paz Public Market 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: La Paz Public Market | Statement: [La Paz batchoy, traditionallySoldAt, La Paz Public Market]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traditionallySoldAt
Context triple: [La Paz batchoy, traditionallySoldAt, La Paz Public Market]
  • A. isSoldIn
    Indicates that a product or item is available for purchase within a specified location, market, or sales channel.
  • B. soldAt chosen
    Indicates that a product or item is offered for sale at a particular location, venue, or outlet.
  • C. isTypicallySoldAs
    Indicates that one entity is commonly offered for sale in the form, packaging, or configuration represented by another entity.
  • D. soldFrom
    Indicates that something was transferred in a sale originating from a particular source, such as a seller, location, or organization.
  • E. notSoldIn
    Indicates that a product or item is unavailable for purchase within a specified market, region, or sales channel.
  • F. None of above.

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_69e2d7f197588190889a03e620558059 completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f29944bea081908f8a732495d67cfc completed April 29, 2026, 11:50 p.m.
PD Predicate disambiguation batch_69f287d76c7c81909494f12e606a9149 completed April 29, 2026, 10:36 p.m.
Created at: April 18, 2026, 2:20 a.m.