Triple
T24123086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-3 |
E597716
|
entity |
| Predicate | containsASCII |
P5716
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ISO/IEC 8859-3, containsASCII, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsASCII Context triple: [ISO/IEC 8859-3, containsASCII, yes]
-
A.
hasAsci
Indicates that one entity possesses or is associated with a specific ASCII representation of another entity.
-
B.
hasUnicode
Indicates that an entity is associated with, represented by, or encoded using a specific Unicode character or sequence.
-
C.
containsCharacter
chosen
Indicates that one entity includes a specific character as part of its content or composition.
-
D.
hasNoConventionalCharacters
Indicates that the entity contains no standard alphanumeric or commonly used written characters.
-
E.
hasTraditionalEnglishCharacter
Indicates that something possesses qualities, features, or style typically associated with traditional English culture or heritage.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee5937c819092396751c23553ca |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:06 p.m.