Triple
T20069475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atimonan, Quezon |
E499694
|
entity |
| Predicate | hasFishingCommunity |
P102582
|
FINISHED |
| Object | small-scale fishers |
—
|
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: small-scale fishers | Statement: [Atimonan, Quezon, hasFishingCommunity, small-scale fishers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFishingCommunity Context triple: [Atimonan, Quezon, hasFishingCommunity, small-scale fishers]
-
A.
hasFishingCommunities
chosen
Indicates that there exist communities in a given area or entity whose livelihoods or primary activities are based on fishing.
-
B.
hasFishingBoats
Indicates that one entity possesses, operates, or is associated with one or more fishing boats.
-
C.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
D.
containsFishery
Indicates that one entity includes, encompasses, or has within its area a fishery or fishing-related operation.
-
E.
hasFishingAccess
Indicates that an entity is permitted or able to fish in or otherwise use a particular water body or fishing area.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e664365ad0819089103b00d1cf8c9f |
completed | April 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:39 p.m.