Triple
T21569522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Leichhardt |
E532247
|
entity |
| Predicate | hasAgricultureIndustry |
P40002
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Division of Leichhardt, hasAgricultureIndustry, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgricultureIndustry Context triple: [Division of Leichhardt, hasAgricultureIndustry, yes]
-
A.
hasAgriculturalProduction
Indicates that an entity engages in or is characterized by the production of agricultural goods such as crops or livestock.
-
B.
hasAgriculturalCharacter
chosen
Indicates that something possesses qualities, features, or uses typical of agriculture or farming activities.
-
C.
hasAgriculturalType
Indicates that an entity is associated with or classified by a specific type or category of agriculture.
-
D.
hasRuralEconomySector
Indicates that an entity participates in, contains, or is associated with an economic sector based on rural activities or rural development.
-
E.
hasAgriculturalAssociation
Indicates that there exists a formal or recognized connection between an entity and an agricultural organization, group, or activity.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cb9718819094fc95b25df68bd1 |
completed | April 27, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.