Triple
T18277090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Foshan |
E437763
|
entity |
| Predicate | isInlandDistanceToSea |
P15760
|
FINISHED |
| Object | approximately 100 kilometers from the South China Sea |
—
|
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: approximately 100 kilometers from the South China Sea | Statement: [Port of Foshan, isInlandDistanceToSea, approximately 100 kilometers from the South China Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInlandDistanceToSea Context triple: [Port of Foshan, isInlandDistanceToSea, approximately 100 kilometers from the South China Sea]
-
A.
distanceFromCoast
chosen
Indicates the measured spatial separation between a location and the nearest point on a coastline.
-
B.
isInlandFrom
Indicates that one place lies away from the coast, further toward the interior of the land, relative to another place.
-
C.
distanceFromMainland
Indicates the measured spatial separation between a location and the nearest point on the mainland.
-
D.
distanceToPacificOcean
Indicates the physical distance between a given location or entity and the Pacific Ocean.
-
E.
hasNearbyCoast
Indicates that one location is situated close to a coastline or seashore.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500528bb88190a9f9ba6428cc2076 |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.