Triple
T12762421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Series ring |
E305026
|
entity |
| Predicate | marketValue |
P36319
|
FINISHED |
| Object | high resale value on collectors market |
—
|
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: high resale value on collectors market | Statement: [World Series ring, marketValue, high resale value on collectors market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketValue Context triple: [World Series ring, marketValue, high resale value on collectors market]
-
A.
haveHighMarketValue
chosen
Indicates that an entity possesses a relatively high monetary worth or price in the marketplace compared to similar entities.
-
B.
monetaryValue
Indicates the amount of money associated with an entity, event, or transaction.
-
C.
marketStatus
Indicates the current trading or availability condition of an asset, product, or market (e.g., open, closed, active, suspended).
-
D.
valueInUSD
Indicates that a given amount or asset is expressed or evaluated in terms of its monetary value in United States dollars (USD).
-
E.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8f9f588190bffdea878856204b |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:28 p.m.