Triple
T24755782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moengo |
E619281
|
entity |
| Predicate | hasArtFestival |
P2955
|
FINISHED |
| Object | Moengo Festival of Visual Arts |
—
|
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: Moengo Festival of Visual Arts | Statement: [Moengo, hasArtFestival, Moengo Festival of Visual Arts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtFestival Context triple: [Moengo, hasArtFestival, Moengo Festival of Visual Arts]
-
A.
hasFestival
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
-
B.
hasCulturalEvent
chosen
Indicates that a cultural event (such as a festival, performance, or exhibition) takes place in, is associated with, or is hosted by a given entity.
-
C.
hasArtScene
Indicates that a place or community possesses an active or notable community of artistic activity, events, and institutions.
-
D.
hasFestivalSection
Indicates that something includes or is associated with a specific section or category within a festival.
-
E.
hasFestivalAttraction
Indicates that a festival includes or features a particular attraction as part of its offerings.
- 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 4:26 a.m.