Triple
T4276963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jupyter Notebook |
E97066
|
entity |
| Predicate | supportsInteractiveWidgets |
P55150
|
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: [Jupyter Notebook, supportsInteractiveWidgets, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInteractiveWidgets Context triple: [Jupyter Notebook, supportsInteractiveWidgets, true]
-
A.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
B.
supportsMultipleWindows
Indicates that the subject can handle or display more than one window or view simultaneously.
-
C.
supportsView
Indicates that one entity provides the capability to display, render, or present another entity in a particular view or format.
-
D.
hasTouchControls
Indicates that an entity supports or is operated through touch-based input controls.
-
E.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
- 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_69b34544be3c819084d1ab82d29f90c5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3501d677481909e7416a1d2b0008c |
completed | March 12, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69b347faa45481908c19c29fb906dc92 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:07 p.m.