Triple
T17597200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhoushan City |
E428603
|
entity |
| Predicate | isMajorFishingBase |
P36081
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Zhoushan City, isMajorFishingBase, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorFishingBase Context triple: [Zhoushan City, isMajorFishingBase, true]
-
A.
isFishingPort
chosen
Indicates that a location functions primarily as a port where fishing vessels operate and fish-related activities such as landing, processing, or trading catch take place.
-
B.
containsFishery
Indicates that one entity includes, encompasses, or has within its area a fishery or fishing-related operation.
-
C.
isMajorSeaport
Indicates that a location functions as a primary maritime port handling significant volumes of sea-based trade, transport, or shipping activity.
-
D.
isMajorDeepWaterAreaOf
Indicates that one area constitutes a primary or significant deep-water region of another area or entity.
-
E.
hasFishingCommunities
Indicates that there exist communities in a given area or entity whose livelihoods or primary activities are based on fishing.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469ecfb108190a9e7a5b380f8ab93 |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.