Triple
T2011641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emerald |
E43698
|
entity |
| Predicate | clarityCharacteristic |
P662
|
FINISHED |
| Object | Frequently included |
—
|
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: Frequently included | Statement: [Emerald, clarityCharacteristic, Frequently included]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clarityCharacteristic Context triple: [Emerald, clarityCharacteristic, Frequently included]
-
A.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
B.
lightingCharacteristic
Indicates the specific qualities or properties of how something is lit, such as brightness, color, direction, or style of illumination.
-
C.
hasLuster
Indicates that one entity possesses a shiny, glossy, or reflective surface quality.
-
D.
hasWaterClarity
Indicates the degree to which water in a given context is clear, transparent, or free from visible impurities.
-
E.
pricingCharacteristic
Indicates how the price of something is determined, structured, or behaves (e.g., fixed, variable, discounted, tiered).
- 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.