Triple
T36986892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stuff.co.nz |
E914987
|
entity |
| Predicate | isMajorOutletIn |
P196729
|
FINISHED |
| Object | New Zealand online news market |
—
|
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: New Zealand online news market | Statement: [Stuff.co.nz, isMajorOutletIn, New Zealand online news market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorOutletIn Context triple: [Stuff.co.nz, isMajorOutletIn, New Zealand online news market]
-
A.
isMajorStoreIn
Indicates that a store has a significant or primary presence or operation within a specified location or area.
-
B.
majorOutletOf
Indicates that one entity serves as a primary distribution or sales channel for another entity’s products or services.
-
C.
majorOutlet
Indicates that an entity functions as a primary or significant distribution or publication channel for another entity.
-
D.
isMajorTransferHubIn
Indicates that a location functions as a primary node where significant volumes of transfers or connections occur within a specified area or network.
-
E.
hasOutlet
Indicates that one entity provides, contains, or is equipped with an outlet or point of access for another entity.
- F. None of above. chosen
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_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
| PDg | Predicate description generation | batch_69fe629a8d4c8190b4aa4dee39efc0a6 |
completed | May 8, 2026, 10:24 p.m. |
Created at: May 3, 2026, 4:14 p.m.