Triple
T31965183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ensign Flandry |
E816154
|
entity |
| Predicate | hasCoverArtInSomeEditionsBy |
P179500
|
FINISHED |
| Object | Michael Whelan |
E272577
|
NE 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: Michael Whelan | Statement: [Ensign Flandry, hasCoverArtInSomeEditionsBy, Michael Whelan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoverArtInSomeEditionsBy Context triple: [Ensign Flandry, hasCoverArtInSomeEditionsBy, Michael Whelan]
-
A.
hasCoverArtFeaturing
Indicates that one entity’s cover art visually features or depicts another entity.
-
B.
hasCoverArtVariant
Indicates that an item has an alternative version of its cover artwork distinct from the primary cover.
-
C.
isCoverArtFor
Indicates that one item serves as the cover artwork or visual representation for another item, such as a publication, recording, or product.
-
D.
coverArtVariesByEdition
chosen
Indicates that the cover artwork of an item is different depending on the specific edition.
-
E.
hasCoverVersionsCount
Indicates the number of distinct cover versions that exist for a given original work or recording.
- F. None of above.
Provenance (4 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0346b487088190814e4bd0765cb609 |
completed | May 12, 2026, 3:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39b40ce980819087f4ae51f6dd47a2 |
completed | June 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_6a0346428c60819090e5ea815c0921ca |
completed | May 12, 2026, 3:24 p.m. |
Created at: May 1, 2026, 12:09 a.m.