Triple
T24704157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jangsaengpo Port |
E611840
|
entity |
| Predicate | changeOfFunction |
P6654
|
FINISHED |
| Object | from commercial whaling base to tourism hub |
—
|
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: from commercial whaling base to tourism hub | Statement: [Jangsaengpo Port, changeOfFunction, from commercial whaling base to tourism hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changeOfFunction Context triple: [Jangsaengpo Port, changeOfFunction, from commercial whaling base to tourism hub]
-
A.
functionChange
chosen
Indicates that an entity’s function, role, or operational behavior has been altered from one state or purpose to another.
-
B.
changesWith
Indicates that one entity varies or is modified in response to changes in another entity.
-
C.
changeType
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
-
D.
changesProperty
Indicates that one entity causes a change in a specific property or attribute of another entity.
-
E.
limitsOnChange
Indicates that there are constraints or restrictions placed on how much or in what ways something may be altered or modified.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:23 a.m.