Triple
T14565509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 東沙環礁 |
E341773
|
entity |
| Predicate | 海洋生態特徵 |
P11765
|
FINISHED |
| Object | 珊瑚礁生態系豐富 |
—
|
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: 珊瑚礁生態系豐富 | Statement: [東沙環礁, 海洋生態特徵, 珊瑚礁生態系豐富]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 海洋生態特徵 Context triple: [東沙環礁, 海洋生態特徵, 珊瑚礁生態系豐富]
-
A.
hasAquaticEcosystem
Indicates that an entity possesses, contains, or is associated with an ecosystem primarily based in water (such as rivers, lakes, wetlands, or oceans).
-
B.
hasMarineEcosystem
chosen
Indicates that an entity possesses, contains, or is associated with a marine ecosystem as part of its characteristics or environment.
-
C.
hasMarineEcoregion
Indicates that an entity is associated with, or located within, a specific marine ecoregion.
-
D.
oceanographicFeature
Indicates that one entity is an oceanographic feature (such as a current, front, eddy, or water mass) associated with or characterizing another entity.
-
E.
hasMarineHabitatType
Indicates that an entity is associated with or occurs in a specific type of marine habitat.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb38c6350819091090ffd15772f6f |
completed | April 14, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.