Triple
T5096653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chalcis |
E114881
|
entity |
| Predicate | alphabetVariant |
P51274
|
FINISHED |
| Object | Chalcidian alphabet |
—
|
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: Chalcidian alphabet | Statement: [Chalcis, alphabetVariant, Chalcidian alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alphabetVariant Context triple: [Chalcis, alphabetVariant, Chalcidian alphabet]
-
A.
alphabetType
chosen
Indicates the type or classification of an alphabet used by a writing system or language.
-
B.
orthographicVariant
Indicates that two written forms are different spellings or orthographic representations of the same linguistic item.
-
C.
alternativeTransliteration
Indicates that one written form represents an alternative way of transliterating the same original text or name into another script or orthography.
-
D.
hasDistinctLetterForms
Indicates that the related writing system or symbol set uses different visual shapes or styles for the same letter in different contexts (such as position, case, or usage).
-
E.
usesAlphabet
Indicates that one entity employs or is written using the alphabet or writing system associated with 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75669afc81908a8db897fe56eccd |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.