Triple
T12249413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riverland |
E291932
|
entity |
| Predicate | isMajorContributorTo |
P32799
|
FINISHED |
| Object | South Australian wine production |
—
|
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: South Australian wine production | Statement: [Riverland, isMajorContributorTo, South Australian wine production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorContributorTo Context triple: [Riverland, isMajorContributorTo, South Australian wine production]
-
A.
hasContributionFrom
Indicates that something (such as a work, project, or outcome) is created, influenced, or supported in part by a specified contributor.
-
B.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
C.
firstContributor
Indicates that the subject is the earliest or initial contributor to the object within a given context or project.
-
D.
isMajorSourceOf
chosen
Indicates that one entity serves as a primary or dominant origin, cause, or provider of another entity or effect.
-
E.
influentialMember
Indicates that an entity plays a significant, impactful, or leading role within a group, organization, or community.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.