Triple
T22656234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menuet II |
E559232
|
entity |
| Predicate | premiereWorkYear |
P149082
|
FINISHED |
| Object | 1749 |
—
|
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: 1749 | Statement: [Menuet II, premiereWorkYear, 1749]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premiereWorkYear Context triple: [Menuet II, premiereWorkYear, 1749]
-
A.
workYear
Indicates the specific year or span of years during which an entity (such as a person or organization) was engaged in work or employment.
-
B.
hasExperienceOf
Indicates that one entity has undergone, encountered, or lived through a particular event, situation, or activity associated with another entity.
-
C.
basedOnWorkFromYear
Indicates that something is derived from, adapted from, or otherwise based on a work that originated in a specified year.
-
D.
previousWorkReleaseYear
Indicates the year in which an earlier or prior work in a sequence or related set was released.
-
E.
timeInCareer
Indicates the point or duration within an entity’s professional or occupational trajectory at which a related event, status, or condition occurs.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765b93dc8190a0357dd4b6ae524a |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:06 p.m.