Triple
T30083320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norfolk Rhapsodies |
E764531
|
entity |
| Predicate | firstPerformanceYearOfPart |
P99128
|
FINISHED |
| Object | 1906 |
—
|
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: 1906 | Statement: [Norfolk Rhapsodies, firstPerformanceYearOfPart, 1906]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPerformanceYearOfPart Context triple: [Norfolk Rhapsodies, firstPerformanceYearOfPart, 1906]
-
A.
firstPrototypeYear
Indicates the year in which the first prototype of an entity was created or completed.
-
B.
firstArrivalYear
Indicates the calendar year in which an entity first arrived at or was initially present in a specified place or context.
-
C.
firstProductionYear
Indicates the year in which something (such as a product, work, or item) was first produced.
-
D.
firstPerformanceOfWorkYear
chosen
Indicates that the referenced performance is the first time a particular work was performed in a given calendar year.
-
E.
yearOfPerformance
Indicates the specific calendar year in which a performance, event, or action took place.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0189f3f0248190a1b018164d18e6f5 |
completed | May 11, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_6a0187ee0920819097047bb55e1f9506 |
completed | May 11, 2026, 7:40 a.m. |
Created at: April 29, 2026, 7:03 p.m.