Triple
T16647125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Sea Power |
E404494
|
entity |
| Predicate | knownForStageDecor |
P25320
|
FINISHED |
| Object | foliage and flags |
—
|
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: foliage and flags | Statement: [British Sea Power, knownForStageDecor, foliage and flags]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForStageDecor Context triple: [British Sea Power, knownForStageDecor, foliage and flags]
-
A.
stageDesigner
chosen
Indicates that one entity is responsible for designing or creating the stage or set for a performance or event in relation to another entity.
-
B.
notableStage
Indicates that an entity is recognized as an important or distinguished stage or phase in relation to another entity or process.
-
C.
knownForCostumes
Indicates that an entity is recognized or notable specifically for its costumes, such as their design, creation, or distinctive use.
-
D.
usedStage
Indicates that an entity made use of a particular stage or phase within a process, workflow, or lifecycle.
-
E.
notableStageArea
Indicates that an entity is recognized as a significant or prominent stage or performance area associated with another entity.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ad66fe88190be582b81719f2ac1 |
completed | April 18, 2026, 12:36 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.