Triple
T15660285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jilong |
E376548
|
entity |
| Predicate | portRankInTaiwan |
P20612
|
FINISHED |
| Object | one of the major international seaports |
—
|
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: one of the major international seaports | Statement: [Jilong, portRankInTaiwan, one of the major international seaports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portRankInTaiwan Context triple: [Jilong, portRankInTaiwan, one of the major international seaports]
-
A.
hasAreaRankInTaiwan
Indicates the relative ranking of an entity by its area size compared to other entities within Taiwan.
-
B.
portRank
chosen
Indicates the relative importance or hierarchical ranking assigned to a port within a given system or context.
-
C.
areaRankInMalaysia
Indicates the relative position of an entity in a size-based ranking by area within Malaysia.
-
D.
distanceFromTaiwanMainIsland
Indicates the measured spatial distance between an entity’s location and the main island of Taiwan.
-
E.
rankInChineseAdministrativeHierarchy
Indicates the relative level or position an administrative unit holds within the formal hierarchy of Chinese government administration.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ef4e6a08190ad8bbafaa3612f22 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.