Triple
T38015869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nine Radio |
E948495
|
entity |
| Predicate | hasSisterCompany |
P3457
|
FINISHED |
| Object | Nine Network |
—
|
NE NERFINISHED |
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: Nine Network | Statement: [Nine Radio, hasSisterCompany, Nine Network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSisterCompany Context triple: [Nine Radio, hasSisterCompany, Nine Network]
-
A.
hasSisterOrganization
chosen
Indicates that one organization is related to another as a sister organization, typically sharing a common parent, affiliation, or parallel status within the same overarching structure.
-
B.
hasParentCompany
Indicates that one company is owned or controlled by another company that serves as its parent organization.
-
C.
hasSisterAirline
Indicates that one airline is related to another as its sister airline, typically sharing common ownership, management, or branding.
-
D.
hasNumberOfSisterOrganizations
Indicates the count of sister or peer organizations associated with a given organization.
-
E.
hasSubsidiariesIn
Indicates that an entity has subsidiary companies or organizations operating or registered in a specified location or jurisdiction.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: May 3, 2026, 4:20 p.m.