Triple
T19913433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PAX-AM |
E478603
|
entity |
| Predicate | hasImprintCharacteristics |
P8008
|
FINISHED |
| Object | artist-owned brand |
—
|
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: artist-owned brand | Statement: [PAX-AM, hasImprintCharacteristics, artist-owned brand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImprintCharacteristics Context triple: [PAX-AM, hasImprintCharacteristics, artist-owned brand]
-
A.
hasImprintStyle
Indicates that one entity bears or exhibits a particular style, pattern, or form of imprint associated with another entity.
-
B.
hasImprintType
chosen
Indicates that an entity (such as a publication or product) is associated with a specific type or category of imprint.
-
C.
hasImprintVariant
Indicates that one imprint (a specific published form of a work) is a variant version of another imprint.
-
D.
hasImprintStatus
Indicates that an entity has a particular imprint-related status or condition assigned to it.
-
E.
includesImprint
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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659917fdc8190bf29bfdab0fe8f85 |
completed | April 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.