Triple
T556955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Riverina |
E11962
|
entity |
| Predicate | hasPrimaryIndustry |
P13077
|
FINISHED |
| Object | agriculture |
—
|
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: agriculture | Statement: [Division of Riverina, hasPrimaryIndustry, agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryIndustry Context triple: [Division of Riverina, hasPrimaryIndustry, agriculture]
-
A.
hasPrincipalIndustry
chosen
Indicates that an entity’s main or primary industry of operation is the specified industry.
-
B.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
C.
isMajorIndustrialEconomy
Indicates that an entity is one of the world’s leading industrialized economies, characterized by large-scale industrial output and significant influence in global economic activity.
-
D.
industryOfUnderlyingCompany
Indicates the industry sector in which the underlying company associated with this entity operates.
-
E.
hasMajorEmployer
Indicates that an entity has a primary or most significant employer with which it is chiefly affiliated for work or occupation.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4991ef9b0819092ec0407270373f4 |
completed | March 1, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69a494bd78e8819083c519669158f209 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.