Triple
T1719482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Win32 API |
E37357
|
entity |
| Predicate | abstractionLevel |
P11425
|
FINISHED |
| Object | low-level |
—
|
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: low-level | Statement: [Win32 API, abstractionLevel, low-level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abstractionLevel Context triple: [Win32 API, abstractionLevel, low-level]
-
A.
automationLevel
Indicates the degree to which a process, task, or system is performed automatically rather than manually.
-
B.
representationLevel
Indicates the degree or layer at which something stands in for, models, or symbolizes something else (e.g., more concrete vs. more abstract representation).
-
C.
logicalLevel
chosen
Indicates the relative position or depth of something within a hierarchy of abstraction, reasoning, or logical structure.
-
D.
classificationLevel
Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
-
E.
documentationLevel
Indicates the extent or thoroughness to which something is described, specified, or supported by written or recorded documentation.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab5c96db6c8190a745d6fef7bf2cdb |
completed | March 6, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69aa61bed2fc819086d912cd34285978 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.