Triple
T31464884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HamNoSys |
E802696
|
entity |
| Predicate | encodingStyle |
P28140
|
FINISHED |
| Object | symbolic |
—
|
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: symbolic | Statement: [HamNoSys, encodingStyle, symbolic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encodingStyle Context triple: [HamNoSys, encodingStyle, symbolic]
-
A.
serializationStyle
Indicates how data is formatted, structured, and encoded when being converted to or from a serialized representation.
-
B.
bindingStyle
Indicates the method or format by which two components, systems, or interfaces are connected or integrated for interaction.
-
C.
syntaxStyle
Indicates the stylistic or structural conventions used in the form or arrangement of an expression, statement, or code.
-
D.
encodingStructure
chosen
Indicates the structural scheme or format used to encode information or data.
-
E.
conformanceStyle
Indicates the specific manner, pattern, or set of rules by which something adheres to or complies with a given standard or specification.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:22 p.m.