Triple
T35052588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shire of Lake Grace |
E1011371
|
entity |
| Predicate | hasPrimaryProduction |
P10569
|
FINISHED |
| Object | wheat |
—
|
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: wheat | Statement: [Shire of Lake Grace, hasPrimaryProduction, wheat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryProduction Context triple: [Shire of Lake Grace, hasPrimaryProduction, wheat]
-
A.
hasPrimaryProductionLocation
Indicates that an entity’s main or principal place where it is produced or manufactured is a specified location.
-
B.
hasProduction
Indicates that an entity is associated with, or responsible for, the creation or manufacture of another entity or product.
-
C.
hasProductionBase
Indicates that one entity serves as the primary location or base where another entity’s production or manufacturing activities are carried out.
-
D.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
E.
hasMajorProductionSystem
chosen
Indicates that an entity primarily operates, utilizes, or is characterized by a particular major production system.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0356f541b08190b40469aa628087f4 |
completed | May 12, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_6a03569e4fa881909c57351a6c489636 |
completed | May 12, 2026, 4:34 p.m. |
Created at: May 3, 2026, 4:01 p.m.