Triple
T23387697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-11 |
E593927
|
entity |
| Predicate | encodingSpace |
P43701
|
FINISHED |
| Object | 8-bit byte |
—
|
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: 8-bit byte | Statement: [ISO/IEC 8859-11, encodingSpace, 8-bit byte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encodingSpace Context triple: [ISO/IEC 8859-11, encodingSpace, 8-bit byte]
-
A.
usesSpace
Indicates that one entity occupies, consumes, or makes use of physical or conceptual space associated with another entity.
-
B.
baseSpacePreserved
Indicates that a mapping between fiber bundles preserves the underlying base space, leaving the base points unchanged.
-
C.
isWrittenWithSpace
Indicates that something is written or represented with spaces separating its components or elements.
-
D.
encodingScope
chosen
Indicates the range or extent of content or information that is covered, represented, or captured by a particular encoding.
-
E.
hasSpaceIn
Indicates that one entity occupies or is contained within a physical or conceptual space provided by 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a498fd08819085e90a872d9d0c7a |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:35 p.m.