Triple
T24151148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-14 |
E598535
|
entity |
| Predicate | hasMIBenum |
P83801
|
FINISHED |
| Object | ISO-8859-14 |
—
|
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-8859-14 | Statement: [ISO/IEC 8859-14, hasMIBenum, ISO-8859-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMIBenum Context triple: [ISO/IEC 8859-14, hasMIBenum, ISO-8859-14]
-
A.
definesMIBFor
Indicates that one entity specifies or establishes the Management Information Base (MIB) used by another entity.
-
B.
definesMIBModule
chosen
Indicates that one entity specifies or establishes the structure and contents of a particular MIB (Management Information Base) module for network management.
-
C.
hasMorseForN
Indicates a relationship where an entity is associated with the Morse code representation corresponding to the letter "N".
-
D.
hasTextualConvention
Indicates that one entity defines or uses a specific standardized textual format or convention for representing information associated with another entity.
-
E.
hasMIC
Indicates that an entity has a specified Minimum Inhibitory Concentration (MIC) value in relation to an antimicrobial agent.
- 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.