Triple
T18376687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oltu stone |
E446336
|
entity |
| Predicate | gloss |
P97872
|
FINISHED |
| Object | glossy |
—
|
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: glossy | Statement: [Oltu stone, gloss, glossy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gloss Context triple: [Oltu stone, gloss, glossy]
-
A.
hasGlossonym
Indicates a relationship where an entity is associated with the specific name or term used to refer to a language (its glossonym).
-
B.
meaningGloss
Indicates that the predicate provides a brief explanatory phrase or paraphrase capturing the meaning or sense of another expression or item.
-
C.
hasEnglishGloss
chosen
Indicates that one entity serves as the English-language gloss or explanatory translation for the other entity.
-
D.
glaze
Indicates that an agent coats or covers a surface of an entity with a smooth, often shiny or protective, layer or substance.
-
E.
gens
Indicates a relationship where one entity generates, produces, or gives rise 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5179849d08190a3ffb9edc633d2ee |
completed | April 19, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:45 a.m.