Triple
T24151141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-14 |
E598535
|
entity |
| Predicate | hasControlCharactersFrom |
P23703
|
FINISHED |
| Object | ISO/IEC 6429 |
—
|
NE NERFINISHED |
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/IEC 6429 | Statement: [ISO/IEC 8859-14, hasControlCharactersFrom, ISO/IEC 6429]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControlCharactersFrom Context triple: [ISO/IEC 8859-14, hasControlCharactersFrom, ISO/IEC 6429]
-
A.
hasControlCharacterRange
chosen
Indicates that there exists a specified range of control characters associated with or applicable to an entity.
-
B.
hasSpecialCharacter
Indicates that a given entity (such as a string or identifier) contains at least one non-alphanumeric special character.
-
C.
hasProtectedCharacter
Indicates that an entity possesses a characteristic or attribute that is legally or formally designated as protected from discrimination or adverse treatment.
-
D.
hasCharacters
Indicates that an entity (such as a work or story) includes or features certain characters as part of its content.
-
E.
hasNoConventionalCharacters
Indicates that the entity contains no standard alphanumeric or commonly used written characters.
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e108308190ba8740590a1c5130 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:30 p.m.