Triple
T19673871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin letter W |
E472400
|
entity |
| Predicate | alphabetMembership |
P20857
|
FINISHED |
| Object | ISO basic Latin 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: ISO basic Latin alphabet | Statement: [Latin letter W, alphabetMembership, ISO basic Latin alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alphabetMembership Context triple: [Latin letter W, alphabetMembership, ISO basic Latin alphabet]
-
A.
alphabet
chosen
Indicates that one entity is an alphabet or set of symbols used for representing elements (such as characters or tokens) in relation to another entity.
-
B.
alphabetRange
Indicates that one entity specifies a contiguous range of letters in an alphabet that extends from the starting letter to the ending letter.
-
C.
alphabeticStatus
Indicates the relative ordering or position of entities based on alphabetical sequence.
-
D.
alphabetic
Indicates that the characters in a string or sequence consist solely of letters from an alphabet, with no digits or special symbols.
-
E.
alphabetType
Indicates the type or classification of an alphabet used by a writing system or language.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6416e19d881909248c4f778f7147a |
completed | April 20, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69e514eb37b8819091502cc954f70eba |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.