Triple
T14883421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queensland marine parks estate |
E350056
|
entity |
| Predicate | managesUse |
P3020
|
FINISHED |
| Object | recreational fishing |
—
|
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: recreational fishing | Statement: [Queensland marine parks estate, managesUse, recreational fishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesUse Context triple: [Queensland marine parks estate, managesUse, recreational fishing]
-
A.
regulatesUse
chosen
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
-
B.
managementIs
Indicates that one entity holds a managerial role, responsibility, or authority over another entity.
-
C.
manageThrough
Indicates that one entity exercises control, direction, or administration over another entity or process by means of an intermediary entity, channel, or mechanism.
-
D.
usesManagementTool
Indicates that one entity employs or operates a management tool to perform or support its management-related activities.
-
E.
modeManaged
Indicates that one entity controls, configures, or oversees the operational mode or state of 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5f4598081908735e8d7dfce8074 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:56 a.m.