Triple
T35141783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TCustomCheckBox |
E1014714
|
entity |
| Predicate | usedInIDE |
P197999
|
FINISHED |
| Object | Embarcadero Delphi |
—
|
NE NERFINISHED |
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: Embarcadero Delphi | Statement: [TCustomCheckBox, usedInIDE, Embarcadero Delphi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInIDE Context triple: [TCustomCheckBox, usedInIDE, Embarcadero Delphi]
-
A.
usedInProject
Indicates that something (such as a resource, tool, or component) is employed or utilized within a particular project.
-
B.
usedInLanguageFeature
Indicates that something (such as a construct, pattern, or element) is employed as a feature within a particular language.
-
C.
usedInMethod
Indicates that something (such as a component, variable, or resource) is utilized or referenced within the execution or implementation of a particular method.
-
D.
usedInInterface
Indicates that something is employed or incorporated as a component or element within a user interface.
-
E.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
- F. None of above. chosen
Provenance (4 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_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
| PDg | Predicate description generation | batch_69fec00e5c1c819083d174bb4bc35f29 |
completed | May 9, 2026, 5:03 a.m. |
Created at: May 3, 2026, 4:02 p.m.