Triple
T20161664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Button Up Your Overcoat |
E491719
|
entity |
| Predicate | isStandardOfEra |
P34280
|
FINISHED |
| Object | Tin Pan Alley era |
—
|
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: Tin Pan Alley era | Statement: [Button Up Your Overcoat, isStandardOfEra, Tin Pan Alley era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStandardOfEra Context triple: [Button Up Your Overcoat, isStandardOfEra, Tin Pan Alley era]
-
A.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
B.
representsEra
Indicates that one entity designates the historical era, period, or age to which another entity belongs or is associated.
-
C.
isStandardOf
chosen
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
D.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
E.
hasPrimaryEra
Indicates that an entity is chiefly associated with or belongs to a particular historical or temporal era.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667e505888190a05e26a3c5a0ede1 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:34 p.m.