Triple
T26119862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganyu District |
E658930
|
entity |
| Predicate | hasMaritimeActivities |
P49505
|
FINISHED |
| Object | fishing |
—
|
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: fishing | Statement: [Ganyu District, hasMaritimeActivities, fishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritimeActivities Context triple: [Ganyu District, hasMaritimeActivities, fishing]
-
A.
maritimeActivity
chosen
Indicates activities, operations, or behaviors that take place at sea or are directly related to maritime environments and navigation.
-
B.
hasMaritimeConnection
Indicates a relationship in which an entity is linked to seas, oceans, or maritime activities, such as shipping, navigation, or coastal operations.
-
C.
hasHarbourActivity
Indicates that a location is the site of harbour-related operations or activities, such as docking, loading, unloading, or servicing vessels.
-
D.
hasMaritimeZone
Indicates that one entity possesses or is associated with a specific maritime area or jurisdictional sea zone.
-
E.
hasMaritimeFeature
Indicates that one entity possesses, contains, or is characterized by a maritime-related feature such as a sea, coast, harbor, or other oceanic element.
- 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 26, 2026, 8:07 p.m.