Triple
T27666757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTSP |
E697246
|
entity |
| Predicate | usesURI |
P162930
|
FINISHED |
| Object | rtsp:// |
—
|
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: rtsp:// | Statement: [RTSP, usesURI, rtsp://]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesURI Context triple: [RTSP, usesURI, rtsp://]
-
A.
usesScheme
Indicates that one entity employs, follows, or is based on a particular scheme, method, or structured plan associated with another entity.
-
B.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
C.
namespaceURI
Indicates the URI that defines the namespace to which a given identifier, element, or resource belongs.
-
D.
usesHost
Indicates that one entity makes use of another entity as its host or hosting environment in order to function, operate, or reside.
-
E.
hasURN
Indicates that an entity is associated with a specific Uniform Resource Name (URN) that uniquely identifies it.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f634a50f3481908954bd4b691d6f19 |
completed | May 2, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f6305219f08190b55f6193a4a49984 |
completed | May 2, 2026, 5:11 p.m. |
Created at: April 27, 2026, 2:38 p.m.