Triple
T29128447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 長良川 |
E738298
|
entity |
| Predicate | cormorantFishingLocation |
P161059
|
FINISHED |
| Object | Gifu City |
E2066824
|
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: Gifu City | Statement: [長良川, cormorantFishingLocation, Gifu City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cormorantFishingLocation Context triple: [長良川, cormorantFishingLocation, Gifu City]
-
A.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
-
B.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
C.
isFishingArea
chosen
Indicates that a location or region is designated or used as an area where fishing activities take place.
-
D.
fishingPort
Indicates that a location functions as a port primarily used for fishing activities, such as landing, processing, or servicing fishing vessels.
-
E.
birdwatchingFeature
Indicates a feature, characteristic, or amenity that is specifically related to or beneficial for birdwatching activities.
- F. None of above.
Provenance (4 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6622c2e1c819093b43ecb65f3fa52 |
completed | May 2, 2026, 8:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a7bd8a8f6e081909c7b1258c490f6e2 |
completed | Aug. 12, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:30 a.m.