Triple
T27041425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Galician Connection (project) |
E684499
|
entity |
| Predicate | performsInContext |
P99079
|
FINISHED |
| Object | concerts |
—
|
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: concerts | Statement: [The Galician Connection (project), performsInContext, concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsInContext Context triple: [The Galician Connection (project), performsInContext, concerts]
-
A.
performedInContextOf
chosen
Indicates that an action or event was carried out within, and is meaningfully related to, a specific situational, procedural, or environmental context.
-
B.
performsAt
Indicates that an entity carries out or presents a performance at a specific location, venue, or event.
-
C.
performsAs
Indicates that one entity takes on, enacts, or fulfills the role, function, or character of another entity.
-
D.
implementedInContextOf
Indicates that something (such as a method, feature, or process) is carried out or realized within a particular surrounding situation, framework, or set of conditions.
-
E.
hasPerformanceContext
Indicates that an entity is associated with a specific performance-related situation, setting, or set of conditions under which it operates or is evaluated.
- 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_69ef148193c48190bb1a0cfae6a407c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 8:05 a.m.