Triple
T35142184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGroupBox |
E1014722
|
entity |
| Predicate | supportsChildControls |
P54128
|
FINISHED |
| Object | True |
—
|
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: True | Statement: [TGroupBox, supportsChildControls, True]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsChildControls Context triple: [TGroupBox, supportsChildControls, True]
-
A.
includesControlType
Indicates that one entity encompasses or specifies a particular type of control within its scope or definition.
-
B.
controlsWith
Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
-
C.
hasChildrenArea
Indicates that an entity includes or is associated with a designated area intended for children.
-
D.
hasControlElement
chosen
Indicates that one entity includes or is associated with a component specifically intended to control, regulate, or influence its behavior or operation.
-
E.
supportsControllerInput
Indicates that an entity is capable of receiving and handling input from a controller device.
- 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_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.