Triple
T29029319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hebrew Melodies, Op. 9 |
E737682
|
entity |
| Predicate | hasKeyInformation |
P176317
|
FINISHED |
| Object | multiple keys |
—
|
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: multiple keys | Statement: [Hebrew Melodies, Op. 9, hasKeyInformation, multiple keys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyInformation Context triple: [Hebrew Melodies, Op. 9, hasKeyInformation, multiple keys]
-
A.
hasKeyMessage
Indicates that one entity conveys, contains, or is associated with a primary or central message of another entity.
-
B.
hasKeyCoverage
Indicates that one entity’s key or set of keys provides coverage, access, or applicability over another entity or domain.
-
C.
hasKeyImage
Indicates that one entity is designated as the primary or representative image associated with another entity.
-
D.
hasKeyPoint
Indicates that one entity includes, contains, or is associated with a specific key point or main idea represented by another entity.
-
E.
hasKeyAccord
Indicates that one entity possesses or defines the primary key or governing agreement that authorizes or controls another entity.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 28, 2026, 9:54 a.m.