Triple
T28675134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Switched-On Brandenburgs |
E725841
|
entity |
| Predicate | hasWorkTitleElement |
P183493
|
FINISHED |
| Object | Brandenburgs |
—
|
NE NERFINISHED |
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: Brandenburgs | Statement: [Switched-On Brandenburgs, hasWorkTitleElement, Brandenburgs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkTitleElement Context triple: [Switched-On Brandenburgs, hasWorkTitleElement, Brandenburgs]
-
A.
hasTitleWork
Indicates that an entity is associated with a specific work by its title (i.e., the entity has or bears that work’s title).
-
B.
hasWorkingTitle
Indicates that an entity is associated with a provisional or temporary title used during its development or production.
-
C.
hasWorkTitlePattern
Indicates that an entity’s work title follows or matches a specified pattern or structured format.
-
D.
hasWorkTitleVariant
Indicates that an entity has an alternative or variant form of its work title, such as a different wording, spelling, or language version of the same title.
-
E.
hasWorkingTitleStatus
Indicates that an entity currently holds the status of having a provisional or working title rather than a finalized official title.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: April 28, 2026, 5:06 a.m.