Triple
T25592527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seven Group Holdings |
E641559
|
entity |
| Predicate | majorInterestIn |
P44657
|
FINISHED |
| Object | Seven West Media |
—
|
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: Seven West Media | Statement: [Seven Group Holdings, majorInterestIn, Seven West Media]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorInterestIn Context triple: [Seven Group Holdings, majorInterestIn, Seven West Media]
-
A.
primaryInterest
chosen
Indicates that one entity is the main or most significant focus of attention, concern, or engagement for another entity.
-
B.
subjectInterest
Indicates that the subject has an interest in, or is concerned with, the object.
-
C.
secondaryInterest
Indicates that an entity has a secondary, less primary but still relevant interest or focus in relation to another entity or topic.
-
D.
interestMayBe
Indicates that one entity potentially has an interest in, or may be interested in, another entity or subject.
-
E.
recognizedInterest
Indicates that one entity has formally acknowledged or identified another entity’s interest in something as valid or relevant.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 21, 2026, 4:25 p.m.