Triple
T23313038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2960 |
E590631
|
entity |
| Predicate | streamCountCapability |
P53675
|
FINISHED |
| Object | multiple independent streams per association |
—
|
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: multiple independent streams per association | Statement: [RFC 2960, streamCountCapability, multiple independent streams per association]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streamCountCapability Context triple: [RFC 2960, streamCountCapability, multiple independent streams per association]
-
A.
hasNumberOfStreams
Indicates the quantity of streams associated with a given entity.
-
B.
hasStreaming
Indicates that an entity provides or supports streaming access to another entity (such as media, data, or content).
-
C.
supportsMultipleStreams
chosen
Indicates that the subject is capable of handling or maintaining more than one data or communication stream at the same time.
-
D.
streams
Indicates that one entity continuously transmits or delivers data, media, or content in real time to another entity.
-
E.
hasStreamingAvailability
Indicates that a media item is available to be streamed through a particular streaming service or platform.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972ca70481909e2415c65964210a |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:06 p.m.