Triple
T30150952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 黄浦江 |
E766392
|
entity |
| Predicate | 地理坐标系 |
P130515
|
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.
hasGeographicalCoordinateSystem
chosen
Indicates that something uses or is defined within a specific geographical coordinate system for locating positions on the Earth’s surface.
-
B.
geodeticReference
Indicates a relationship where one spatial or geographic entity is defined, measured, or located with respect to a specific geodetic reference system or datum.
-
C.
coordinateReferenceSystemType
Indicates the specific kind or category of coordinate reference system (e.g., geographic, projected, vertical) associated with a spatial dataset or geometry.
-
D.
planetographicCoordinateSystem
Indicates a relationship where an object's position is specified using a coordinate system tied to a planet's surface geometry and reference features.
-
E.
coordinateSystem
Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed4297c81909062f19b7795f181 |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:20 p.m.