Triple
T9115941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arkenstone of Thrain |
E218718
|
entity |
| Predicate | highlyValuedBy |
P38308
|
FINISHED |
| Object | dwarves |
—
|
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: dwarves | Statement: [Arkenstone of Thrain, highlyValuedBy, dwarves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highlyValuedBy Context triple: [Arkenstone of Thrain, highlyValuedBy, dwarves]
-
A.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
-
B.
isHighlyPrized
chosen
Indicates that something is regarded with exceptional value, admiration, or importance, often being especially sought after or cherished.
-
C.
haveHighMarketValue
Indicates that an entity possesses a relatively high monetary worth or price in the marketplace compared to similar entities.
-
D.
hasHighRatingOn
Indicates that one entity is evaluated or reviewed on another entity’s platform or system with a rating that meets or exceeds a defined high threshold.
-
E.
isValuedFor
Indicates that one entity is appreciated, esteemed, or considered important because of a particular quality, contribution, or characteristic it provides to 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_69ca83dc94ac8190b9ef42684d36ff39 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a1340881909dc791b825e87ef2 |
completed | April 1, 2026, 5:09 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:16 p.m.