Triple
T33425911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | About a Quarter to Nine |
E855973
|
entity |
| Predicate | hasApproximateYearOfComposition |
P114755
|
FINISHED |
| Object | 1934 |
—
|
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: 1934 | Statement: [About a Quarter to Nine, hasApproximateYearOfComposition, 1934]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateYearOfComposition Context triple: [About a Quarter to Nine, hasApproximateYearOfComposition, 1934]
-
A.
hasUnknownExactDateOfComposition
Indicates that the precise date when a work was composed is not known.
-
B.
approximateYearWritten
chosen
Indicates the estimated calendar year in which something was written, when the exact year is not known.
-
C.
probableCenturyOfComposition
Indicates the century in which something (typically a work or composition) was most likely created or written.
-
D.
approximateStartYear
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
-
E.
circaComposition
Indicates that one entity was composed or created around, but not exactly on, the time associated with another entity.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 1, 2026, 1:36 a.m.