Triple
T13019303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TForm |
E322633
|
entity |
| Predicate | baseClassFor |
P2421
|
FINISHED |
| Object | application main windows |
—
|
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: application main windows | Statement: [TForm, baseClassFor, application main windows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseClassFor Context triple: [TForm, baseClassFor, application main windows]
-
A.
baseType
Indicates that one entity serves as the underlying or parent type from which another entity is derived or specialized.
-
B.
isBaseFor
chosen
Indicates that one entity serves as the foundational support, starting point, or underlying basis upon which another entity is built, developed, or depends.
-
C.
classBelow
Indicates that one class is positioned lower than another in a hierarchy, ordering, or structural arrangement.
-
D.
usesBase
Indicates that one entity relies on or operates using another entity as its foundational resource, framework, or reference point.
-
E.
associatedBase
Indicates a relationship where one entity is linked or connected to a corresponding base entity that it depends on or is derived from.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ecf21bc819082fb512bc479b4be |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:51 p.m.