Triple
T6034225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTCRtpEncodingParameters |
E134377
|
entity |
| Predicate | propertyType_codecPayloadType |
P8440
|
FINISHED |
| Object | byte |
—
|
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: byte | Statement: [RTCRtpEncodingParameters, propertyType_codecPayloadType, byte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyType_codecPayloadType Context triple: [RTCRtpEncodingParameters, propertyType_codecPayloadType, byte]
-
A.
payloadType
chosen
Indicates the kind or category of payload associated with or carried by an entity or action.
-
B.
partCType
Indicates that an entity is classified as a specific subtype or category of a larger part or component.
-
C.
propagatorType
Indicates the specific method or model used to propagate or advance a state (such as position, condition, or effect) from one point in time or space to another.
-
D.
codeType
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
E.
hasPropertyType
Indicates that an entity possesses or is associated with a specific type or category of property.
- 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056b220608190b156be95632cf3b3 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.