Triple
T8686704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qubee orthography |
E206177
|
entity |
| Predicate | usesDigraphs |
P54131
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Qubee orthography, usesDigraphs, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDigraphs Context triple: [Qubee orthography, usesDigraphs, true]
-
A.
usesDigraph
Indicates that one entity employs or represents information using a directed graph structure, where relationships have a specified direction.
-
B.
hasDigraph
chosen
Indicates that one entity is associated with or represented by a specific digraph (a two-character sequence treated as a single unit).
-
C.
usesDiacritics
Indicates that the referenced text or linguistic element employs diacritical marks as part of its written form.
-
D.
usesTrigraph
Indicates that one entity employs or incorporates a trigraph (a three-character sequence representing a single unit, such as a sound or symbol) in relation to another entity or context.
-
E.
usesAlphabet
Indicates that one entity employs or is written using the alphabet or writing system associated with another entity.
- 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:33 p.m.