Triple
T14565517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 東沙環礁 |
E341773
|
entity |
| Predicate | 國家公園成立時間 |
P14062
|
FINISHED |
| Object | 2007年1月17日公告成立的國家公園範圍 |
—
|
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: 2007年1月17日公告成立的國家公園範圍 | Statement: [東沙環礁, 國家公園成立時間, 2007年1月17日公告成立的國家公園範圍]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 國家公園成立時間 Context triple: [東沙環礁, 國家公園成立時間, 2007年1月17日公告成立的國家公園範圍]
-
A.
dateEstablishedAsNationalPark
chosen
Indicates the date on which a location or area was officially designated as a national park.
-
B.
stateParkEstablishedFor
Indicates that a state park was created or designated for the benefit, use, or purpose of a particular entity or objective.
-
C.
establishedAsPark
Indicates that an area or site has been officially designated and recognized as a park.
-
D.
establishedAsNationalParkBy
Indicates that an area or site was officially designated and created as a national park through the action or authority of a specific person, organization, or governmental body.
-
E.
establishedAsUnitOfNationalParkSystem
Indicates that an area or site was formally designated and incorporated as a unit within the national park system.
- 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.