Triple
T8867567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashmore Reef |
E211056
|
entity |
| Predicate | fishingRegulations |
P51236
|
FINISHED |
| Object | commercial fishing prohibited |
—
|
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: commercial fishing prohibited | Statement: [Ashmore Reef, fishingRegulations, commercial fishing prohibited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fishingRegulations Context triple: [Ashmore Reef, fishingRegulations, commercial fishing prohibited]
-
A.
fishingPolicy
chosen
Indicates the rules, regulations, or management approach governing fishing activities and resource use.
-
B.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
-
C.
fishingType
Indicates the specific method or style of fishing associated with an activity, event, or location.
-
D.
commercialFishingAllowed
Indicates that engaging in commercial fishing activities is permitted in the specified area or context.
-
E.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
- 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_69ca838d3c7c8190a849566d5afd2b11 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6108530c819084559f4de669ce20 |
completed | April 1, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:51 p.m.