Triple

T23195309
Position Surface form Disambiguated ID Type / Status
Subject Overseas Missionary Fellowship E579855 entity
Predicate hasGlobalBase P60372 FINISHED
Object sending countries worldwide 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: sending countries worldwide | Statement: [Overseas Missionary Fellowship, hasGlobalBase, sending countries worldwide]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGlobalBase
Context triple: [Overseas Missionary Fellowship, hasGlobalBase, sending countries worldwide]
  • A. hasGlobalHost
    Indicates that an entity is associated with or served by a host that is accessible or applicable at a global (system-wide or worldwide) level.
  • B. hasGlobalRegion
    Indicates that an entity is associated with or belongs to a specific global geographic region.
  • C. hasSupportBaseIn chosen
    Indicates that one entity maintains an operational or organizational base of support located in another entity.
  • D. hasBaseSystem
    Indicates that one entity is founded upon, derived from, or primarily operates using another entity as its underlying system or framework.
  • E. hasBaseRegion
    Indicates that one entity is situated upon, supported by, or primarily associated with a specific underlying region or area.
  • 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_69e24600eed08190bd7e5295653a1503 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18fdb279c81908dcc46f2786a86cd completed April 29, 2026, 4:58 a.m.
PD Predicate disambiguation batch_69ef8a041c0081909afb670d17a5aaba completed April 27, 2026, 4:08 p.m.
Created at: April 17, 2026, 4:06 p.m.