Triple
T1515529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ugaritic alphabet |
E32109
|
entity |
| Predicate | numberOfVowelSigns |
P4430
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Ugaritic alphabet, numberOfVowelSigns, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfVowelSigns Context triple: [Ugaritic alphabet, numberOfVowelSigns, 3]
-
A.
hasNumberOfVowelLetters
chosen
Indicates that an entity is associated with a specific count of vowel letters it contains.
-
B.
containsVowelLetters
Indicates that the subject includes one or more vowel letters within its sequence of characters.
-
C.
hasDistinctVowelLetters
Indicates that the subject contains vowel letters that are all different from one another, with no vowel repeated.
-
D.
hasVowelNotationSystem
Indicates that a writing or transcription system for a language includes a method for explicitly representing vowel sounds.
-
E.
hasVowelFeature
Indicates that an entity possesses a specific vowel-related phonological or articulatory feature.
- 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_69a885e8caf88190a5fbb6159ce87786 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9396e16408190b5e7b0ac43376d81 |
completed | March 5, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69a907aa67cc81909f00135365447399 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.