Triple
T27793611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ga Traditional Council |
E701146
|
entity |
| Predicate | overseesFestival |
P24921
|
FINISHED |
| Object | Homowo festival |
—
|
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: Homowo festival | Statement: [Ga Traditional Council, overseesFestival, Homowo festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesFestival Context triple: [Ga Traditional Council, overseesFestival, Homowo festival]
-
A.
festivalOrganiser
Indicates that one entity is responsible for planning, coordinating, or managing a festival for another entity or context.
-
B.
operatesFestival
chosen
Indicates that one entity manages and runs the organization or execution of a festival for another entity or in a particular context.
-
C.
festivalSystem
Indicates a relationship where an entity is part of, managed by, or associated with a festival-related organizational or operational system.
-
D.
determinesFestival
Indicates that one entity decides, defines, or selects which festival is applicable or will occur for another entity or context.
-
E.
mainFestival
Indicates that an event is the primary or central festival associated with a particular context, place, or entity.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 5:29 p.m.