Triple
T34839154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port MacDonnell |
E1004284
|
entity |
| Predicate | fishingSeasonImportant |
P78242
|
FINISHED |
| Object | rock lobster season |
—
|
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: rock lobster season | Statement: [Port MacDonnell, fishingSeasonImportant, rock lobster season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fishingSeasonImportant Context triple: [Port MacDonnell, fishingSeasonImportant, rock lobster season]
-
A.
hasFishingSeason
chosen
Indicates that there is a defined time period during which fishing for a particular resource or in a particular area is permitted or regulated.
-
B.
fishingImportance
Indicates the degree to which fishing plays a significant or prioritized role in relation to a given entity or context.
-
C.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
-
D.
fishingPolicy
Indicates the rules, regulations, or management approach governing fishing activities and resource use.
-
E.
fishingUse
Indicates that one entity uses another as a tool, method, or context specifically for the activity of fishing.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.