Triple
T36986982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macquarie Radio Network |
E914990
|
entity |
| Predicate | operatedRadioStation |
P42386
|
FINISHED |
| Object | 2GB |
E948496
|
NE 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: 2GB | Statement: [Macquarie Radio Network, operatedRadioStation, 2GB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedRadioStation Context triple: [Macquarie Radio Network, operatedRadioStation, 2GB]
-
A.
formerRadioStation
Indicates that the subject was once a radio station but no longer operates in that capacity.
-
B.
hasRadioStation
Indicates that one entity possesses, operates, or is served by a particular radio station.
-
C.
operatedStation
chosen
Indicates that one entity managed, ran, or was responsible for the operation of a particular station.
-
D.
hasFictionalRadioStation
Indicates that an entity includes, features, or is associated with a fictional radio station within its context or content.
-
E.
radioOperator
Indicates a relationship where one entity serves as the radio operator for another, handling radio communication duties on its behalf.
- F. None of above.
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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a01d7b3ce8c8190b2f90be730505765 |
completed | May 11, 2026, 1:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e575c55e081909dd64a3b32ab4e92 |
completed | June 26, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_6a01d5115a6c8190a6d9f96ec484135a |
completed | May 11, 2026, 1:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.