Triple
T26830479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I'll See You Again |
E675485
|
entity |
| Predicate | isStandardFromEra |
P77920
|
FINISHED |
| Object | 1920s popular song repertoire |
—
|
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: 1920s popular song repertoire | Statement: [I'll See You Again, isStandardFromEra, 1920s popular song repertoire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStandardFromEra Context triple: [I'll See You Again, isStandardFromEra, 1920s popular song repertoire]
-
A.
representsEra
Indicates that one entity designates the historical era, period, or age to which another entity belongs or is associated.
-
B.
preservesEra
Indicates that something maintains or keeps intact the characteristics, style, or conditions of a particular historical period.
-
C.
hasPrimaryEra
chosen
Indicates that an entity is chiefly associated with or belongs to a particular historical or temporal era.
-
D.
standardizedInCentury
Indicates that something was standardized or formally established according to a common norm during a specified century.
-
E.
prefersEra
Indicates a relationship where one entity favors or is more inclined toward a particular historical or cultural era over others.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61adc60c88190924d7b71d52851e8 |
completed | May 2, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:01 a.m.