Triple
T37388754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 广州国际金融城（规划） |
E928643
|
entity |
| Predicate | 规划层级 |
P33672
|
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.
urbanPlanningLevel
Indicates the degree or quality of planning, organization, and regulation applied to the development and use of urban spaces.
-
B.
hasPlanningLevel
chosen
Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
-
C.
planningControl
Indicates that an authority or agent exercises regulatory oversight or decision-making power over how something is planned, developed, or used.
-
D.
planStructure
Indicates that one entity defines or organizes the internal arrangement, components, or layout of another entity.
-
E.
plannedStructure
Indicates that one entity is a structure that is intended or designed to be built or established in the future, rather than already existing.
- 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.