Triple
T19720164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagara River |
E473585
|
entity |
| Predicate | cormorantFishingPracticedAt |
P81811
|
FINISHED |
| Object | Gifu City |
—
|
NE NERFINISHED |
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: [Nagara River, cormorantFishingPracticedAt, Gifu City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cormorantFishingPracticedAt Context triple: [Nagara River, cormorantFishingPracticedAt, Gifu City]
-
A.
historicallyFishedBy
Indicates that an area or body of water has been used for fishing by a particular entity or group in the past.
-
B.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
-
C.
fishedFor
Indicates that one entity attempted to catch another entity (typically an animal or resource) by engaging in fishing activities.
-
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.
fishingType
chosen
Indicates the specific method or style of fishing associated with an activity, event, or location.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e64410e5548190b60e13603b6c0053 |
completed | April 20, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.