Triple
T22814114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTCRtpHeaderExtensionParameters |
E565056
|
entity |
| Predicate | propertyType_uri |
P149832
|
FINISHED |
| Object | DOMString |
—
|
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: DOMString | Statement: [RTCRtpHeaderExtensionParameters, propertyType_uri, DOMString]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyType_uri Context triple: [RTCRtpHeaderExtensionParameters, propertyType_uri, DOMString]
-
A.
propertyType_rid
Indicates that an entity is associated with a specific property type identified by a unique resource identifier (RID).
-
B.
propertiesType
Indicates that one entity is classified as a specific type or category of properties associated with another entity.
-
C.
propertyType_rtx
Indicates that one entity has a specific type or category of property in relation to another entity.
-
D.
propertyTypeSpecialization
Indicates that one property type is a more specific or specialized version of another, more general property type.
-
E.
propertyTypeOwned
Indicates that one entity owns a specific type or category of property in relation to 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d62b0ec8190ac22909192e8a876 |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:32 p.m.