Triple
T35142178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGroupBox |
E1014722
|
entity |
| Predicate | hasAncestorUnit |
P47433
|
FINISHED |
| Object | Vcl.Controls |
—
|
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: Vcl.Controls | Statement: [TGroupBox, hasAncestorUnit, Vcl.Controls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestorUnit Context triple: [TGroupBox, hasAncestorUnit, Vcl.Controls]
-
A.
hasAncestor
Indicates that one entity is an ancestor (direct or indirect, such as a parent, grandparent, etc.) of another entity in a genealogical or hierarchical lineage.
-
B.
hasParentUnit
chosen
Indicates that one unit is hierarchically contained within or belongs to another, higher-level unit.
-
C.
hasAncestralTo
Indicates that one entity is an ancestor of another, existing in an earlier generation within a lineage or heritage chain.
-
D.
hasISOAncestor
Indicates that an entity is derived from, based on, or descended from a specified ISO (International Organization for Standardization) standard or specification.
-
E.
hasHierarchyAbove
Indicates that one entity occupies a higher or superior level in an ordered structure or chain of command relative to 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_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 3, 2026, 4:02 p.m.