Triple
T19915007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | writing the novel "Watership Down" |
E478641
|
entity |
| Predicate | hasMarketPositionOfResult |
P137795
|
FINISHED |
| Object | bestseller |
—
|
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: bestseller | Statement: [writing the novel "Watership Down", hasMarketPositionOfResult, bestseller]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarketPositionOfResult Context triple: [writing the novel "Watership Down", hasMarketPositionOfResult, bestseller]
-
A.
hasMarketStatus
Indicates the current commercial or trading condition of an entity, such as whether it is active, suspended, listed, or delisted in a market.
-
B.
hasStockPosition
Indicates that an entity holds a quantity of a particular stock, typically specifying ownership, size, and possibly direction (long or short) of the investment position.
-
C.
hasMarketRole
Indicates that an entity holds or performs a specific functional role within a market or marketplace context.
-
D.
hasMarket
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
E.
hasMarketIndex
Indicates that an entity is associated with, or tracked by, a specific market index.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6599394f081909246006c2e83bacc |
completed | April 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:53 p.m.