Triple
T32180075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hmng |
E821954
|
entity |
| Predicate | codeUsageContext |
P37480
|
FINISHED |
| Object | information technology |
—
|
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: information technology | Statement: [Hmng, codeUsageContext, information technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeUsageContext Context triple: [Hmng, codeUsageContext, information technology]
-
A.
modernUsageContext
Indicates the contemporary or current context in which something is used, applied, or functions.
-
B.
hasTypicalUseContext
chosen
Indicates that something is commonly or characteristically used within a particular situation, setting, or context.
-
C.
originalUseContext
Indicates the original situation, setting, or context in which something was intended to be used or applied.
-
D.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
E.
keyUsageContext
Indicates the specific circumstances, purposes, or operational conditions under which a key is intended or permitted to be used.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba7cbc708190ab91b828e5ef2976 |
completed | May 3, 2026, 3:01 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:34 a.m.