Triple
T31649544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aspen MLT |
E807678
|
entity |
| Predicate | hasImprintOrLine |
P129165
|
FINISHED |
| Object | Aspen Showcase |
—
|
NE NERFINISHED |
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: Aspen Showcase | Statement: [Aspen MLT, hasImprintOrLine, Aspen Showcase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImprintOrLine Context triple: [Aspen MLT, hasImprintOrLine, Aspen Showcase]
-
A.
hasImprintType
Indicates that an entity (such as a publication or product) is associated with a specific type or category of imprint.
-
B.
hasImprintStyle
Indicates that one entity bears or exhibits a particular style, pattern, or form of imprint associated with another entity.
-
C.
hasImprintStatus
Indicates that an entity has a particular imprint-related status or condition assigned to it.
-
D.
hasImprintVariant
Indicates that one imprint (a specific published form of a work) is a variant version of another imprint.
-
E.
includesImprint
chosen
Indicates that one entity contains, incorporates, or carries the imprint or branding of another entity.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 30, 2026, 10:52 p.m.