Triple
T18411532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 南方科技大学 |
E441768
|
entity |
| Predicate | 所在区域发展战略角色 |
P79198
|
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.
strategicRoleIn
Indicates that one entity serves a strategic function, position, or importance within the context, operations, or objectives of another entity.
-
B.
roleInBeltAndRoad
Indicates the specific function, involvement, or capacity an entity has within the context of the Belt and Road Initiative.
-
C.
strategicArea
Indicates that an entity is designated as an area of strategic importance or priority within a broader plan, operation, or context.
-
D.
developmentStrategyRole
chosen
Indicates the role or function an entity plays within a particular development strategy or plan.
-
E.
coordinatesRegionalDevelopment
Indicates overseeing and aligning development activities across different areas or regions to ensure cohesive and balanced regional growth.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51a24e130819082b92f98d8d5fa3c |
completed | April 19, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.