Triple
T5312646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bacup Coconutters |
E119069
|
entity |
| Predicate | hasPerformanceSetting |
P44703
|
FINISHED |
| Object | streets of Bacup |
—
|
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: streets of Bacup | Statement: [Bacup Coconutters, hasPerformanceSetting, streets of Bacup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformanceSetting Context triple: [Bacup Coconutters, hasPerformanceSetting, streets of Bacup]
-
A.
hasSetting
Indicates that an entity takes place, occurs, or exists within a particular environment, context, or location.
-
B.
hasPerformanceConvention
Indicates that there is an agreed-upon set of rules, norms, or standards governing how a particular performance or activity should be carried out.
-
C.
hasMusicalSettingsBy
Indicates that a work has been set to music or musically arranged by a specified creator or composer.
-
D.
hasPerformanceContext
chosen
Indicates that an entity is associated with a specific performance-related situation, setting, or set of conditions under which it operates or is evaluated.
-
E.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
- 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_69bd446b57bc8190a513d2e6c40314f3 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84534f9c8190bc19d4812060768d |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:54 p.m.