Triple
T1166451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTCRtpReceiver |
E24809
|
entity |
| Predicate | hasSpecificationStatus |
P8040
|
FINISHED |
| Object | Recommendation (via WebRTC 1.0) |
—
|
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: Recommendation (via WebRTC 1.0) | Statement: [RTCRtpReceiver, hasSpecificationStatus, Recommendation (via WebRTC 1.0)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecificationStatus Context triple: [RTCRtpReceiver, hasSpecificationStatus, Recommendation (via WebRTC 1.0)]
-
A.
hasSpecification
Indicates that an entity is associated with a particular specification that defines or constrains its properties, behavior, or requirements.
-
B.
hasStatusIn
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
-
C.
hasStatusLabel
Indicates that an entity is associated with a specific status expressed as a human-readable label.
-
D.
standardizationStatus
chosen
Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
-
E.
hadSpecialStatusIn
Indicates that an entity possessed a particular special, exceptional, or non-standard status within a specified context or time period.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bccc62a88190882d8801908015a4 |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb548c1481909092626c572d8782 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.