Triple
T21425012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greeny |
E528529
|
entity |
| Predicate | marketValueCategory |
P18022
|
FINISHED |
| Object | high-value collectors instrument |
—
|
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-value collectors instrument | Statement: [Greeny, marketValueCategory, high-value collectors instrument]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketValueCategory Context triple: [Greeny, marketValueCategory, high-value collectors instrument]
-
A.
priceCategory
chosen
Indicates the classification of an item or service based on its price level or cost range.
-
B.
haveHighMarketValue
Indicates that an entity possesses a relatively high monetary worth or price in the marketplace compared to similar entities.
-
C.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
-
D.
hasValuation
Indicates that an entity is assigned or associated with a specific assessed value or worth.
-
E.
marketClassification
Indicates how an entity is categorized or segmented within a particular market or market structure.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee813c7a048190a400e364c8df1dcf |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:48 p.m.