Triple
T32807354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scene Explorer |
E839054
|
entity |
| Predicate | hasInterfaceElement |
P200846
|
FINISHED |
| Object | tree view |
—
|
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: tree view | Statement: [Scene Explorer, hasInterfaceElement, tree view]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInterfaceElement Context triple: [Scene Explorer, hasInterfaceElement, tree view]
-
A.
hasInterface
Indicates that one entity provides, exposes, or is connected through a defined interface to another entity.
-
B.
hasInterfaceCategory
Indicates that an interface is classified as belonging to a particular category or type of interface.
-
C.
hasElementType
Indicates that something is composed of or contains elements that are of a specified type.
-
D.
isInterface
Indicates that one entity functions as an interface or boundary through which another entity interacts, communicates, or connects with a system or component.
-
E.
usesInterface
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffb1f0b03c81909ddb81f07ce74e88 |
completed | May 9, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ffb1662b2481908582e0612744f4c5 |
completed | May 9, 2026, 10:12 p.m. |
| PDg | Predicate description generation | batch_69ffb1f001948190a63c493b596a97b9 |
completed | May 9, 2026, 10:15 p.m. |
Created at: May 1, 2026, 1:15 a.m.