Triple
T37018368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odis |
E916143
|
entity |
| Predicate | hasOrthographicVariantType |
P198894
|
FINISHED |
| Object | phonetic variant |
—
|
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: phonetic variant | Statement: [Odis, hasOrthographicVariantType, phonetic variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrthographicVariantType Context triple: [Odis, hasOrthographicVariantType, phonetic variant]
-
A.
orthographicVariant
Indicates that two written forms are different spellings or orthographic representations of the same linguistic item.
-
B.
hasOrthographicConvention
Indicates that there is a specific writing or spelling convention that governs how something is represented in written form.
-
C.
hasOrthographicReform
Indicates that an entity has undergone or is associated with a change or standardization in its writing system or spelling conventions.
-
D.
hasOrthographicPreference
Indicates that one entity prefers or selects a particular written or spelling form of another entity.
-
E.
hasOrthographyStatus
Indicates the orthographic status or condition of how something is written or spelled, such as its conformity to a particular writing system or standard.
- F. None of above. chosen
Provenance (4 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
| PDg | Predicate description generation | batch_69ff10956d3881909144f880f92e90c4 |
completed | May 9, 2026, 10:46 a.m. |
Created at: May 3, 2026, 4:14 p.m.