Triple
T29690166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Qt Company |
E751189
|
entity |
| Predicate | hasFrameworkType |
P174398
|
FINISHED |
| Object | cross-platform application framework |
—
|
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: cross-platform application framework | Statement: [The Qt Company, hasFrameworkType, cross-platform application framework]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFrameworkType Context triple: [The Qt Company, hasFrameworkType, cross-platform application framework]
-
A.
hasFrameType
Indicates that an entity possesses or is associated with a specific type or category of frame.
-
B.
hasFrameworkInstrument
Indicates that one entity uses or is associated with a specific framework as the instrument or means for performing an action or achieving a result.
-
C.
hasPackageType
Indicates that an entity is associated with or classified under a particular type or category of package.
-
D.
isPartOfFramework
Indicates that one entity functions as a component, module, or element within a larger structured framework or system.
-
E.
adoptedFrameworkType
Indicates that one entity has chosen and is using a particular framework type as its adopted standard or approach.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6c20f209081909fb9ac8f95069f04 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c125695c81909704c67bef4ce5b2 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 28, 2026, 7:16 p.m.