Triple
T380493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SGML |
E8666
|
entity |
| Predicate | characterSetModel |
P7661
|
FINISHED |
| Object | abstract character set |
—
|
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: abstract character set | Statement: [SGML, characterSetModel, abstract character set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterSetModel Context triple: [SGML, characterSetModel, abstract character set]
-
A.
characterSetType
Indicates the type or category of character set associated with or used by an entity.
-
B.
usesCharacterSet
chosen
Indicates that one entity employs or relies on a specific character set defined by another entity for encoding or representing text.
-
C.
characterBasedOn
Indicates that one character is modeled, inspired, or derived from another real or fictional entity.
-
D.
UnicodeBlock
Indicates that a character belongs to a specific contiguous range of code points defined as a Unicode block.
-
E.
hasGlyphRepertoireSize
Indicates the number of distinct glyphs included in an entity’s glyph repertoire.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2c95088190a603bb1ee076ebd6 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e964d4b481909290e474b0341e3c |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.