Triple
T19688189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenician letter Waw |
E472766
|
entity |
| Predicate | graphemicClass |
P23172
|
FINISHED |
| Object | radical-consonant |
—
|
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: radical-consonant | Statement: [Phoenician letter Waw, graphemicClass, radical-consonant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphemicClass Context triple: [Phoenician letter Waw, graphemicClass, radical-consonant]
-
A.
graphemicUnit
chosen
Indicates a relationship where one element functions as a basic written symbol or character unit within a writing system.
-
B.
graphemeInventory
Indicates the set of distinct written symbols or characters used in a language or writing system.
-
C.
morphologicalClass
Indicates the classification of an entity based on its morphological form or structural pattern.
-
D.
etymologicalClass
Indicates the relationship between a term and the category or type of its origin or historical linguistic development.
-
E.
linguisticClassification
Indicates the relationship by which an entity is categorized according to its language or linguistic type.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420d39688190ad3a84dbffce4ffe |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.