Triple
T2011659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emerald |
E43698
|
entity |
| Predicate | rarityComparedTo |
P19183
|
FINISHED |
| Object | More rare than diamond of similar size and quality |
—
|
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: More rare than diamond of similar size and quality | Statement: [Emerald, rarityComparedTo, More rare than diamond of similar size and quality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rarityComparedTo Context triple: [Emerald, rarityComparedTo, More rare than diamond of similar size and quality]
-
A.
rarity
Indicates how uncommon or infrequently an entity or event occurs relative to others in a given context.
-
B.
frequencyComparedTo
Indicates how often one event or action occurs relative to another, expressing a comparison of their frequencies.
-
C.
rankComparedTo
Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
-
D.
isLessCommonThan
chosen
Indicates that one item occurs, appears, or is observed less frequently than another item.
-
E.
collectionStrength
Indicates the degree or intensity of association or cohesion among items within a collection.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8b150a8819096c919465fd91ab5 |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.