Triple
T30504678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WIMP |
E776234
|
entity |
| Predicate | alternativeFullForm |
P2351
|
FINISHED |
| Object | Windows Icons Menus Pointing device |
—
|
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: Windows Icons Menus Pointing device | Statement: [WIMP, alternativeFullForm, Windows Icons Menus Pointing device]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeFullForm Context triple: [WIMP, alternativeFullForm, Windows Icons Menus Pointing device]
-
A.
alternativeForm
Indicates that one entity is an alternative version, variant, or representation of another entity.
-
B.
alternativeAbbreviation
Indicates that one term serves as an alternative shortened form or acronym for another term.
-
C.
hasFullForm
chosen
Indicates that one entity is the complete, expanded, or unabbreviated form of another entity.
-
D.
expandedForm
Indicates that one representation is the expanded or fully written-out form of another, typically decomposing it into a sum or more detailed expression.
-
E.
alternateDescription
Indicates that an entity has an additional or substitute textual description that can be used in place of its primary description.
- 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 29, 2026, 8:15 p.m.