Triple
T237391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murray River (part) |
E4850
|
entity |
| Predicate | supportsIndustry |
P2186
|
FINISHED |
| Object | horticulture |
—
|
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: horticulture | Statement: [Murray River (part), supportsIndustry, horticulture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsIndustry Context triple: [Murray River (part), supportsIndustry, horticulture]
-
A.
supportsVentureType
Indicates that an entity provides backing, resources, or compatibility for a specified type or category of venture.
-
B.
support
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
-
C.
supportsActivity
chosen
Indicates that one entity provides the necessary conditions, resources, or environment for another entity’s activity to occur or be sustained.
-
D.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
E.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25dacf60c8190a5c3ef455b9a8b20 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b5f27208190ae13f34037fe582b |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.