Triple
T35141728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TCustomListBox |
E1014713
|
entity |
| Predicate | wrapsAPI |
P31856
|
FINISHED |
| Object | Windows list box control |
—
|
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 list box control | Statement: [TCustomListBox, wrapsAPI, Windows list box control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wrapsAPI Context triple: [TCustomListBox, wrapsAPI, Windows list box control]
-
A.
canWrap
Indicates that one entity is able to enclose, cover, or surround another entity, typically forming an outer layer or container around it.
-
B.
wrapsFunctionFamily
Indicates that one function or component encapsulates and delegates behavior to a family of related functions, acting as a wrapper around them.
-
C.
includesAPI
Indicates that one entity provides or contains an application programming interface (API) that can be used by another entity.
-
D.
hasAPIs
chosen
Indicates that one entity provides or exposes application programming interfaces (APIs) that can be used or accessed by another entity.
-
E.
canBeWrappedBy
Indicates that one entity is capable of being enclosed, covered, or surrounded by another entity.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78caa838c8190a7ebc02fe81ecb1c |
completed | May 3, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.