Triple

T36698650
Position Surface form Disambiguated ID Type / Status
Subject pueblo Andoa E906158 entity
Predicate relacionTradicionalCon P44442 FINISHED
Object bosques amazónicos 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: bosques amazónicos | Statement: [pueblo Andoa, relacionTradicionalCon, bosques amazónicos]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relacionTradicionalCon
Context triple: [pueblo Andoa, relacionTradicionalCon, bosques amazónicos]
  • A. traditionAssociatesWith
    Indicates that a particular tradition is connected or linked to another entity, such as a practice, group, place, or concept.
  • B. cognateTradition
    Indicates that two entities belong to the same or closely related cultural, intellectual, or historical tradition, sharing a common origin or lineage.
  • C. hasTraditionalAssociation chosen
    Indicates that one entity is customarily or historically linked with another according to tradition or long-established practice.
  • D. allyRelation
    Indicates a cooperative, supportive relationship in which the entities act as allies toward shared or aligned goals.
  • E. linkedToTradition
    Indicates a relationship where something is connected or related to a particular tradition, heritage, or customary practice.
  • 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_69f76e7195c48190b5580c9cfb01e95f completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fb3425666081908916fcbf3b5dd907 completed May 6, 2026, 12:29 p.m.
PD Predicate disambiguation batch_69fb2f5f3164819099429c2cc3d24e01 completed May 6, 2026, 12:09 p.m.
Created at: May 3, 2026, 4:12 p.m.