Triple
T36410949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chorus (Henry V) |
E896876
|
entity |
| Predicate | workApproximateCompositionYear |
P114755
|
FINISHED |
| Object | 1599 |
—
|
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: 1599 | Statement: [Chorus (Henry V), workApproximateCompositionYear, 1599]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workApproximateCompositionYear Context triple: [Chorus (Henry V), workApproximateCompositionYear, 1599]
-
A.
compositionYear
Indicates the year in which a work (such as a piece of music, art, or literature) was originally created or composed.
-
B.
approximateYearWritten
chosen
Indicates the estimated calendar year in which something was written, when the exact year is not known.
-
C.
approximatePremiereYear
Indicates the estimated calendar year in which something, typically a work or event, first premiered.
-
D.
releaseApproximateYear
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
-
E.
workOriginYear
Indicates the year in which a work (such as a creative, scholarly, or artistic piece) was originally created or first produced.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:10 p.m.