Triple

T36443538
Position Surface form Disambiguated ID Type / Status
Subject Coffea E897801 entity
Predicate canephoraOrigin P185749 FINISHED
Object Central Africa 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: Central Africa | Statement: [Coffea, canephoraOrigin, Central Africa]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canephoraOrigin
Context triple: [Coffea, canephoraOrigin, Central Africa]
  • A. hasApostolicOriginFrom
    Indicates that something (typically a doctrine, tradition, or authority) originates from, or is derived through, the apostles or their foundational teaching.
  • B. coCathedral
    Indicates that a church shares the status and functions of a cathedral with another cathedral within the same diocese or ecclesiastical jurisdiction.
  • C. motherhouseOf
    Indicates that one religious community or congregation serves as the principal or founding house (central residence and administrative center) of another related community.
  • D. canonizedBy
    Indicates that an entity has been officially declared a saint or holy figure by a specified religious authority.
  • E. motherChurch
    Indicates that one church serves as the primary, founding, or supervising church in relation to another church.
  • F. None of above. chosen

Provenance (4 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_69f76e5720b481908f8177ac24a7560b completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c371931c8190afb1d4dd5157f92c completed May 3, 2026, 9:51 p.m.
PD Predicate disambiguation batch_69f7c1b91fd88190ab85afd626603769 completed May 3, 2026, 9:44 p.m.
PDg Predicate description generation batch_69f7c3705b5c81908c84004543a71c07 completed May 3, 2026, 9:51 p.m.
Created at: May 3, 2026, 4:10 p.m.