Triple
T29180831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faust Symphony |
E739739
|
entity |
| Predicate | notableKeyArea |
P66406
|
FINISHED |
| Object | C major |
—
|
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: C major | Statement: [Faust Symphony, notableKeyArea, C major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableKeyArea Context triple: [Faust Symphony, notableKeyArea, C major]
-
A.
notableTargetArea
Indicates that an action, effect, or focus is specifically directed toward a particularly important or prominent area or region.
-
B.
notableOperationArea
Indicates the geographic area or region where an entity primarily conducts or is recognized for its significant operations or activities.
-
C.
notableKey
chosen
Indicates that the referenced key is of particular importance or prominence compared to other keys in the same context.
-
D.
notableAreaWithin
Indicates that one area is a particularly significant or noteworthy part located inside another, larger area.
-
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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a030d3db2748190b32fcf7b21bd0d0a |
completed | May 12, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_6a030ca6bf388190b2f6931376323da3 |
completed | May 12, 2026, 11:19 a.m. |
Created at: April 28, 2026, 11:57 a.m.