Triple
T36970024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Op Roakeldais festival |
E914537
|
entity |
| Predicate | performersOrigin |
P48015
|
FINISHED |
| Object | various countries |
—
|
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: various countries | Statement: [Op Roakeldais festival, performersOrigin, various countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performersOrigin Context triple: [Op Roakeldais festival, performersOrigin, various countries]
-
A.
performerOrigin
Indicates that a performer originates from, or is associated with, a particular place or region.
-
B.
originalPerformerNationality
Indicates the country or national identity associated with the performer who first performed the work or role.
-
C.
originalPerformer
Indicates that an entity is the first or initial performer of a work, role, or performance.
-
D.
participantsOrigin
chosen
Indicates that the relationship specifies the geographic or organizational origin of the participants involved in an event or activity.
-
E.
bringsPerformersFrom
Indicates a relationship where one entity arranges for or causes performers to come from a particular source, place, or group to another context or location.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
Created at: May 3, 2026, 4:14 p.m.