Triple
T24123090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-3 |
E597716
|
entity |
| Predicate | nonBreakingSpaceCode |
P508
|
FINISHED |
| Object | 160 |
—
|
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: 160 | Statement: [ISO/IEC 8859-3, nonBreakingSpaceCode, 160]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonBreakingSpaceCode Context triple: [ISO/IEC 8859-3, nonBreakingSpaceCode, 160]
-
A.
breaksCharacterInFrontOf
Indicates that one entity stops maintaining their in-character behavior or persona in the presence of another entity.
-
B.
usesCodeSpace
Indicates that one entity employs or operates within a particular code space or coding environment provided by another entity.
-
C.
numericCode
chosen
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
D.
notEncodedIn
Indicates that a piece of information, data, or content is explicitly absent from or not represented within a given encoding, format, or medium.
-
E.
breaksOn
Indicates that one entity fractures, shatters, or fails when subjected to contact with or force from 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_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.