Triple
T2968200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obsidian (color) |
E80216
|
entity |
| Predicate | namingInspiredBy |
P24365
|
FINISHED |
| Object | obsidian (volcanic glass) |
—
|
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: obsidian (volcanic glass) | Statement: [Obsidian (color), namingInspiredBy, obsidian (volcanic glass)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingInspiredBy Context triple: [Obsidian (color), namingInspiredBy, obsidian (volcanic glass)]
-
A.
nameGivesRiseTo
Indicates that one name, term, or designation leads to, causes, or results in the emergence or establishment of another.
-
B.
isNamedFor
chosen
Indicates that one entity bears its name in honor of, or derived from, another entity.
-
C.
influencedNameOf
Indicates that one entity has affected or shaped the naming or choice of name of another entity.
-
D.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
E.
isNamedAfterOccupation
Indicates that an entity’s name is derived from or based on a particular occupation or profession.
- 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_69ad8b14ffe881908ffed62f9595c867 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad996fa4388190abd319c69ee583d9 |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.