Triple
T7947087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 双一流 |
E184523
|
entity |
| Predicate | 纳入规划 |
P5176
|
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.
partOfCityPlan
Indicates that something is included as a component or element within a broader city planning scheme or framework.
-
B.
partOfUrbanPlanBy
Indicates that something is included as a component or element within an urban plan created or overseen by a specified agent.
-
C.
plannedUnder
chosen
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
D.
planningControl
Indicates that an authority or agent exercises regulatory oversight or decision-making power over how something is planned, developed, or used.
-
E.
hasPlanningConcept
Indicates that an entity is associated with, defined by, or governed by a particular planning-related concept or framework.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b2abdbc819085ae53826d36af3b |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.