Triple
T12807119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coleambally Irrigation Area |
E306172
|
entity |
| Predicate | hasManagementModel |
P18551
|
FINISHED |
| Object | farmer-owned co-operative |
—
|
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: farmer-owned co-operative | Statement: [Coleambally Irrigation Area, hasManagementModel, farmer-owned co-operative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManagementModel Context triple: [Coleambally Irrigation Area, hasManagementModel, farmer-owned co-operative]
-
A.
hasManagement
Indicates that one entity exercises managerial authority or oversight over another entity.
-
B.
hasTypeOfManagement
chosen
Indicates that an entity is associated with or operates under a specified form or style of management.
-
C.
isManaged
Indicates that one entity exercises supervisory or administrative control over another entity.
-
D.
isManagedFor
Indicates that one entity is administered, overseen, or controlled on behalf of another entity or purpose.
-
E.
hasStationManagement
Indicates that one entity is responsible for managing, operating, or overseeing the activities and administration of a station associated with another entity.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e808130819080f404b3a7462c2e |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.