Triple

T34172910
Position Surface form Disambiguated ID Type / Status
Subject peso E876589 entity
Predicate typicalSubdivisionValue P112029 FINISHED
Object 100 centavos LITERAL 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: 100 centavos | Statement: [peso, typicalSubdivisionValue, 100 centavos]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalSubdivisionValue
Context triple: [peso, typicalSubdivisionValue, 100 centavos]
  • A. hasSubdivisionTypical
    Indicates that an entity typically has a particular kind of subdivision as a characteristic or representative part of its structure.
  • B. typicalSubunitOf chosen
    Indicates that something is a standard or commonly occurring subcomponent or part of a larger whole.
  • C. hasSubdivisionStandard
    Indicates that a governing standard or specification defines how an entity is to be subdivided into smaller parts or units.
  • D. traditionalSubdivisionOf
    Indicates that one entity is a historically or culturally recognized sub-unit or component region of another, according to traditional (rather than strictly modern administrative) divisions.
  • E. primarySubdivisionOf
    Indicates that one administrative or territorial unit is the main first-level subdivision within a larger political or geographic entity.
  • 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_69f349ad97ac8190bf1f17417c970e64 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_6a037c8ae0248190b7e2ce4bf852c22d completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379f963908190846d232f386fd98f completed May 12, 2026, 7:05 p.m.
Created at: May 1, 2026, 1:54 a.m.