Triple
T9326721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Fine Romance |
E224404
|
entity |
| Predicate | hasNotableRecordingEra |
P22765
|
FINISHED |
| Object | 1940s |
—
|
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: 1940s | Statement: [A Fine Romance, hasNotableRecordingEra, 1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableRecordingEra Context triple: [A Fine Romance, hasNotableRecordingEra, 1940s]
-
A.
recordingEra
chosen
Indicates the historical time period or era during which the recording was made.
-
B.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
-
C.
hasNotableRecordingBy
Indicates that an entity (such as a work or composition) has a well-known or significant recording created or performed by a specified agent (such as an artist, ensemble, or label).
-
D.
reRecordingEra
Indicates that one recording is a new or updated version created in a later era relative to an earlier recording.
-
E.
notableEraNickname
Indicates the informal or popular nickname by which a particular historical era or period is commonly known.
- 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_69ca8427a0c08190b749831d5ea98f02 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd36f88e988190bb896a3d7c3c723c |
completed | April 1, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:39 p.m.