Triple
T27110065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moyola River |
E686686
|
entity |
| Predicate | hasFishingClub |
P183099
|
FINISHED |
| Object | Moyola Angling Association |
E1464665
|
NE 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: Moyola Angling Association | Statement: [Moyola River, hasFishingClub, Moyola Angling Association]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFishingClub Context triple: [Moyola River, hasFishingClub, Moyola Angling Association]
-
A.
hasFishingCommunities
Indicates that there exist communities in a given area or entity whose livelihoods or primary activities are based on fishing.
-
B.
hasPowerboatClub
Indicates that one entity hosts, contains, or is associated with a powerboat club.
-
C.
hasYachtClub
Indicates that an entity possesses, hosts, or is associated with a yacht club.
-
D.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
E.
hasFishingBoats
Indicates that one entity possesses, operates, or is associated with one or more fishing boats.
- F. None of above. chosen
Provenance (5 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f798387ea481909f51303f53a22e52 |
completed | May 3, 2026, 6:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12480e5d5c8190ada377aa10ba5704 |
completed | May 24, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79798663481908d6bc48dd6a94ca6 |
completed | May 3, 2026, 6:44 p.m. |
Created at: April 27, 2026, 8:53 a.m.