Triple
T228208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenician alphabet |
E4356
|
entity |
| Predicate | writingSystemClass |
P9330
|
FINISHED |
| Object | alphabetic |
—
|
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: alphabetic | Statement: [Phoenician alphabet, writingSystemClass, alphabetic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingSystemClass Context triple: [Phoenician alphabet, writingSystemClass, alphabetic]
-
A.
writingSystem
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
B.
writingSystemStatus
Indicates the current functional or sociolinguistic state of a writing system, such as whether it is actively used, obsolete, official, or endangered.
-
C.
replacedWritingSystem
Indicates that one writing system has been superseded or taken the place of another as the primary script used for a language or context.
-
D.
isMostWidelyUsedWritingSystem
Indicates that the subject writing system is used by more people or in more contexts than any other writing system.
-
E.
notationSystem
Indicates a relationship where one entity is the system or method of notation used to represent or encode another entity.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25d10ac248190a98dedabf5358668 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b5877588190af694d060377f027 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25d0ec71081908478c800be4f7bb0 |
completed | Feb. 28, 2026, 3:12 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.