Triple
T9457352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BRS Media |
E228050
|
entity |
| Predicate | domainExtensionTypeOperated |
P52128
|
FINISHED |
| Object | country-code top-level domain |
—
|
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: country-code top-level domain | Statement: [BRS Media, domainExtensionTypeOperated, country-code top-level domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainExtensionTypeOperated Context triple: [BRS Media, domainExtensionTypeOperated, country-code top-level domain]
-
A.
domainServed
Indicates that a particular domain or area is supported, covered, or provided for by a given entity or service.
-
B.
internetDomainTypeManaged
chosen
Indicates that the internet domain is administered or controlled by a managing authority or organization.
-
C.
operatedByCompany
Indicates that an entity is run, managed, or controlled by a specific company.
-
D.
operatesUnderName
Indicates that an entity conducts its activities or business using a particular name, which may differ from its official or legal name.
-
E.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
- 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.