Triple
T27592344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KEDA |
E699811
|
entity |
| Predicate | supportsEventSource |
P203
|
FINISHED |
| Object | Apache Kafka |
—
|
NE NERFINISHED |
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: Apache Kafka | Statement: [KEDA, supportsEventSource, Apache Kafka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsEventSource Context triple: [KEDA, supportsEventSource, Apache Kafka]
-
A.
supportedEvent
Indicates that an entity is capable of recognizing, handling, or being associated with a particular type of event.
-
B.
supportsStreamingIn
Indicates that one entity provides or enables streaming functionality within a specified context, environment, or medium.
-
C.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
D.
supportsMultipleStreams
Indicates that the subject is capable of handling or maintaining more than one data or communication stream at the same time.
-
E.
supportsEventSeries
Indicates that an entity provides the necessary functionality or resources to host, manage, or accommodate a recurring series of related events.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
Created at: April 27, 2026, 2:05 p.m.