Triple
T7930622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACM Computing Classification System |
E184179
|
entity |
| Predicate | topLevelCategoryExample |
P34976
|
FINISHED |
| Object | Hardware |
—
|
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: Hardware | Statement: [ACM Computing Classification System, topLevelCategoryExample, Hardware]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topLevelCategoryExample Context triple: [ACM Computing Classification System, topLevelCategoryExample, Hardware]
-
A.
highestCategory
chosen
Indicates that the related entity is the topmost or most specific category to which another entity is ultimately classified or assigned.
-
B.
canonicalCategory
Indicates that an entity is assigned to its primary or standard category within a classification system.
-
C.
catalogCategory
Indicates that an item or entity is assigned to, or belongs within, a specific catalog category.
-
D.
hasCategoryLevel
Indicates that something is associated with a specific hierarchical category or tier within a classification system.
-
E.
categoryStructure
Indicates the hierarchical or organizational relationship that defines how categories are structured and arranged relative to one another.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3accc388819087065ebe7d5d9591 |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:07 p.m.