Triple
T9457357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BRS Media |
E228050
|
entity |
| Predicate | webPresence |
P18972
|
FINISHED |
| Object | https://brsmedia.fm/ |
—
|
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: https://brsmedia.fm/ | Statement: [BRS Media, webPresence, https://brsmedia.fm/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: webPresence Context triple: [BRS Media, webPresence, https://brsmedia.fm/]
-
A.
onlinePresence
chosen
Indicates that an entity maintains a presence or representation on the internet, such as through websites, profiles, or digital platforms.
-
B.
modernPresence
Indicates that something exists, appears, or is active in the contemporary or present-day context.
-
C.
mediaPresence
Indicates the extent to which something is visible, represented, or covered within various media channels or platforms.
-
D.
globalPresence
Indicates that an entity operates, is represented, or has a significant footprint across multiple countries or world regions.
-
E.
networkPresence
Indicates that an entity is available, reachable, or active within a particular network or set of interconnected systems.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f90cf648190ab238ba6b4f03c4f |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:52 p.m.