Triple

T29687367
Position Surface form Disambiguated ID Type / Status
Subject Copa Verde E751123 entity
Predicate alternativePathwayTo P19868 FINISHED
Object national competitions in Brazil 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: national competitions in Brazil | Statement: [Copa Verde, alternativePathwayTo, national competitions in Brazil]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: alternativePathwayTo
Context triple: [Copa Verde, alternativePathwayTo, national competitions in Brazil]
  • A. alternativeRoute chosen
    Indicates that there exists a different path or option that can be taken instead of the primary or original route.
  • B. alternativeTerminus
    Indicates that something serves as another possible endpoint or final destination in place of, or in addition to, a primary terminus.
  • C. transferPathwayTo
    Indicates the act of moving or reassigning a pathway (such as a process, route, or channel) from one entity to another.
  • D. supportsPathway
    Indicates that one entity contributes to, enables, or maintains the functioning or progression of a specified pathway.
  • E. hasPathway
    Indicates that there exists a route, channel, or sequence of steps through which one entity leads, connects, or gives access to another.
  • 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_69f0d625b09481909b0b69aea1e846c8 completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f6b903538481909cffcb6cc1cc0e70 completed May 3, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69f6b626120c819097c9ad04487570d7 completed May 3, 2026, 2:42 a.m.
Created at: April 28, 2026, 7:14 p.m.