Triple
T30879734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haydn symphonies |
E786577
|
entity |
| Predicate | earliestKeyUsage |
P180548
|
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: [Haydn symphonies, earliestKeyUsage, C major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestKeyUsage Context triple: [Haydn symphonies, earliestKeyUsage, C major]
-
A.
earliestVersionDate
Indicates the date on which the earliest known or first version of an entity was created, released, or became valid.
-
B.
firstUsedAt
Indicates the time or place at which something was initially used or put into operation.
-
C.
earliestEpochOf
Indicates the earliest time point or epoch at which a given entity, event, or state first occurs or becomes valid in relation to another.
-
D.
earliestDate
Indicates the earliest point in time at which an associated event, state, or relationship is considered to begin or be valid.
-
E.
earliestOf
Indicates that one entity occurs or is positioned earlier in time or order than all other entities in a given set.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 29, 2026, 8:48 p.m.