Triple
T3428836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minerva |
E72288
|
entity |
| Predicate | collectability |
P2370
|
FINISHED |
| Object | high among watch enthusiasts |
—
|
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 among watch enthusiasts | Statement: [Minerva, collectability, high among watch enthusiasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectability Context triple: [Minerva, collectability, high among watch enthusiasts]
-
A.
collects
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
-
B.
collectibleAspect
chosen
Indicates that one entity represents a collectible-related characteristic, feature, or dimension associated with another entity.
-
C.
significantCollector
Indicates that an entity plays an important or notable role in collecting items, works, or data related to another entity.
-
D.
numismaticCategory
Indicates the classification or type of a numismatic object (such as a coin, medal, or token) within a numismatic system or taxonomy.
-
E.
rarity
Indicates how uncommon or infrequently an entity or event occurs relative to others in a given context.
- 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9854ca081909e637adcac46a27c |
completed | March 8, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.