Triple
T64764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Italic script |
E1287
|
entity |
| Predicate | scriptType |
P4427
|
FINISHED |
| Object | consonant-vowel 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: consonant-vowel alphabet | Statement: [Old Italic script, scriptType, consonant-vowel alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptType Context triple: [Old Italic script, scriptType, consonant-vowel alphabet]
-
A.
script
Indicates that an entity is associated with a written text or code (such as a screenplay, program, or written instructions) that defines its content or behavior.
-
B.
codeType
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
C.
programType
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
D.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
E.
sessionType
Indicates the classification or category of a particular session based on its purpose, format, or context.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a2516eda54819090f5c14384d4eab1 |
completed | Feb. 28, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69a24ea5c140819080409a968c8d2ce8 |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a2516d98e88190b79261bd3fcadd9b |
completed | Feb. 28, 2026, 2:22 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.