Triple
T1402904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proto-Canaanite script |
E31624
|
entity |
| Predicate | graphemeInventory |
P27605
|
FINISHED |
| Object | consonant signs only |
—
|
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: consonant signs only | Statement: [Proto-Canaanite script, graphemeInventory, consonant signs only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphemeInventory Context triple: [Proto-Canaanite script, graphemeInventory, consonant signs only]
-
A.
graphemicUnit
Indicates a relationship where one element functions as a basic written symbol or character unit within a writing system.
-
B.
diacriticType
Indicates the specific kind or category of diacritic mark associated with a character or symbol.
-
C.
UnicodeStandardVersionIntroduced
Indicates the specific version of the Unicode Standard in which a given character, feature, or property was first introduced.
-
D.
hasPhonemeInventory
Indicates that an entity possesses a specific set or system of distinct speech sounds (phonemes) used in its language.
-
E.
UnicodeBlock
Indicates that a character belongs to a specific contiguous range of code points defined as a Unicode block.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c39ef554819096c17bca5891829b |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c11067b48190bca6ef3ac1475c20 |
completed | March 1, 2026, 10:43 p.m. |
Created at: March 1, 2026, 7:59 p.m.