Triple
T2902524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junkie |
E62684
|
entity |
| Predicate | marketPositionAtRelease |
P42608
|
FINISHED |
| Object | published as pulp paperback |
—
|
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: published as pulp paperback | Statement: [Junkie, marketPositionAtRelease, published as pulp paperback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketPositionAtRelease Context triple: [Junkie, marketPositionAtRelease, published as pulp paperback]
-
A.
marketPosition
Indicates the relative standing or rank an entity holds within a specific market compared to its competitors.
-
B.
marketDebut
Indicates the event or point in time when something (such as a product, service, or asset) is first introduced or made available on the market.
-
C.
introducedInMarket
Indicates that an entity was first made available or launched for sale within a particular market or marketplace.
-
D.
releasedDuring
Indicates that one entity was released within the time period defined by another entity.
-
E.
rankingReleasePeriod
Indicates the time span or date range during which a particular ranking is valid, published, or in effect.
- F. None of above. chosen
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_69ab4c3e070c8190b78d3d2c005876dd |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abe0b3d20881908cd4f1b465b504af |
completed | March 7, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69abdd19bac881908f047d616aca8438 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdd96670c8190b727f9ac27dadf67 |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 10:10 p.m.