Triple
T29691047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | icewmbg |
E751208
|
entity |
| Predicate | packageNameExample |
P57997
|
FINISHED |
| Object | icewm |
—
|
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: icewm | Statement: [icewmbg, packageNameExample, icewm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: packageNameExample Context triple: [icewmbg, packageNameExample, icewm]
-
A.
npmPackageName
Indicates that the subject is identified by, or associated with, a specific package name in the npm (Node Package Manager) ecosystem.
-
B.
packageNameOnPyPI
Indicates that a given software package has the specified name on the Python Package Index (PyPI).
-
C.
importName
Indicates that one entity brings another entity into a scope, module, or context under a specific name used for reference.
-
D.
hasPackageName
chosen
Indicates that an entity (such as a software component or module) is associated with a specific package name identifier.
-
E.
exportName
Indicates that one entity is exported under a specific name or label in relation to another context or system.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6729454bc8190b00ca425f7336a01 |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 7:16 p.m.