Triple
T21424874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Horizon |
E528526
|
entity |
| Predicate | hasNotableReleasePeriod |
P87721
|
FINISHED |
| Object | 1967 |
—
|
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: 1967 | Statement: [Blue Horizon, hasNotableReleasePeriod, 1967]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableReleasePeriod Context triple: [Blue Horizon, hasNotableReleasePeriod, 1967]
-
A.
hasNotableRecordingPeriod
Indicates that an entity is associated with a specific time span during which notable recording activity took place.
-
B.
hasNotableReleaseArtist
Indicates that an entity (such as a release or work) is associated with a notable artist responsible for its creation or performance.
-
C.
hasNotableVersion
Indicates that an entity has a specific version or variant that is particularly significant, distinguished, or noteworthy compared to other versions.
-
D.
hasNotabilityPeriod
Indicates the time span during which an entity is or was notable or prominent.
-
E.
hasNotableYear
chosen
Indicates that an entity is associated with a specific year that is particularly significant or noteworthy for it.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee813b798c8190a379cbf6cc6e14d2 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:48 p.m.