Triple
T18799457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bokeh |
E459723
|
entity |
| Predicate | supportsRealTimeUpdates |
P114849
|
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: [Bokeh, supportsRealTimeUpdates, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRealTimeUpdates Context triple: [Bokeh, supportsRealTimeUpdates, true]
-
A.
supportsRealTime
Indicates that one entity provides or enables real-time operation, processing, or interaction for another entity or process.
-
B.
supportsRealTimeMonitoring
chosen
Indicates that an entity provides the capability to observe and track relevant data or events continuously as they occur in real time.
-
C.
supportsRealTimePresence
Indicates that an entity provides or enables real-time awareness of other users’ current status, activity, or availability.
-
D.
hasRealTimeInformation
Indicates that up-to-date, continuously refreshed information is available about the related entity or event.
-
E.
isCalculatedInRealTime
Indicates that the value or result is computed dynamically at the moment of use rather than being precomputed or stored.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a02273b481909bc250144a0ace32 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.