Triple
T4298991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Glass Mountain |
E99785
|
entity |
| Predicate | surfaceTexture |
P4016
|
FINISHED |
| Object | vitreous |
—
|
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: vitreous | Statement: [Little Glass Mountain, surfaceTexture, vitreous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceTexture Context triple: [Little Glass Mountain, surfaceTexture, vitreous]
-
A.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
-
B.
surfaceState
Indicates the physical condition or status of a surface, such as its texture, cleanliness, damage, or treatment at a given time.
-
C.
surfaceCurrent
Indicates that one entity is the prevailing flow or movement of a fluid (such as water or air) along the surface of another entity.
-
D.
surfaceChange
Indicates a change in the physical surface characteristics or condition of an entity over time or due to some event or interaction.
-
E.
texture
chosen
Indicates the surface quality or feel of an entity as perceived by touch or appearance, such as being smooth, rough, soft, or coarse.
- 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_69b345528ebc8190b5abc7e95094792d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3509d39348190aa83304661230cba |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.