Triple
T25002876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breton alphabet |
E625765
|
entity |
| Predicate | usesUppercase |
P156937
|
FINISHED |
| Object | Latin capital letters |
—
|
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: Latin capital letters | Statement: [Breton alphabet, usesUppercase, Latin capital letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesUppercase Context triple: [Breton alphabet, usesUppercase, Latin capital letters]
-
A.
hasUppercaseUsage
Indicates that an entity is used or represented with uppercase letters in a particular context or form.
-
B.
isUppercasePreferred
Indicates that uppercase letters are favored or expected over other letter cases in a given context.
-
C.
hasUppercase
Indicates that an entity contains at least one uppercase (capital) letter.
-
D.
usesCapitalization
chosen
Indicates that one entity applies specific capitalization (such as upper/lower case or title case) to another entity, typically a string or text element.
-
E.
hasUppercaseForm
Indicates that one textual entity is the uppercase version or representation of another textual 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:05 a.m.