Triple

T299000
Position Surface form Disambiguated ID Type / Status
Subject Order of AHEPA E6156 entity
Predicate hasFoundingPurpose P932 FINISHED
Object to promote Hellenic heritage 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: to promote Hellenic heritage | Statement: [Order of AHEPA, hasFoundingPurpose, to promote Hellenic heritage]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFoundingPurpose
Context triple: [Order of AHEPA, hasFoundingPurpose, to promote Hellenic heritage]
  • A. hasCharterPurpose chosen
    Indicates that an entity’s purpose or mission, as formally defined in its charter or founding document, is the specified objective or activity.
  • B. foundedFor
    Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
  • C. foundedWith
    Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
  • D. foundedAs
    Indicates the original name or form under which an organization, institution, or entity was first established.
  • E. hasMissionStatement
    Indicates that an entity possesses a formal mission statement that articulates its core purpose, goals, or guiding principles.
  • 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_69a2e79114b081909490b3bf5a5dbb51 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2ea0dd1dc8190aecd5afdeb2fd74b completed Feb. 28, 2026, 1:13 p.m.
PD Predicate disambiguation batch_69a2e9398df08190af40063a2de7a1d0 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:06 p.m.