Triple
T28456755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paredes de Coura |
E716732
|
entity |
| Predicate | festivalSetting |
P164741
|
FINISHED |
| Object | natural amphitheatre |
—
|
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: natural amphitheatre | Statement: [Paredes de Coura, festivalSetting, natural amphitheatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalSetting Context triple: [Paredes de Coura, festivalSetting, natural amphitheatre]
-
A.
festivalSystem
Indicates a relationship where an entity is part of, managed by, or associated with a festival-related organizational or operational system.
-
B.
festivalOrganiser
Indicates that one entity is responsible for planning, coordinating, or managing a festival for another entity or context.
-
C.
festivalFeature
Indicates that a festival includes or showcases a particular element, activity, or attraction as one of its features.
-
D.
festivalActivity
Indicates that an entity is an event, performance, or engagement that takes place as part of a festival’s organized program.
-
E.
determinesFestival
Indicates that one entity decides, defines, or selects which festival is applicable or will occur for another entity or context.
- F. None of above. chosen
Provenance (4 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_69efd6b76f8c8190a7ba908aca280942 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64ee0c2788190a94a04ad1902fd5e |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64e36c57c8190af09470a8d35512b |
completed | May 2, 2026, 7:19 p.m. |
Created at: April 28, 2026, 1:54 a.m.