Triple
T33157218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Passing Show of 1937 |
E848612
|
entity |
| Predicate | hasTimePeriodInTitle |
P33319
|
FINISHED |
| Object | 1937 |
—
|
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: 1937 | Statement: [The Passing Show of 1937, hasTimePeriodInTitle, 1937]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimePeriodInTitle Context triple: [The Passing Show of 1937, hasTimePeriodInTitle, 1937]
-
A.
hasPeriodTitles
Indicates that an entity is associated with one or more titles that apply specifically to a defined time period.
-
B.
hasTimePeriodName
Indicates that an entity is associated with a specific named time period (e.g., era, epoch, or historical interval).
-
C.
hasTitleSince
Indicates that an entity has held a particular title continuously starting from a specified point in time.
-
D.
hasYearInTitle
chosen
Indicates that the title of an entity explicitly contains a year value as part of its text.
-
E.
showsTimePeriod
Indicates that one entity presents or displays a specific span or interval of 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_69f3495b02d08190bb3d366823dffc21 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 1:28 a.m.