Triple
T7984165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 211工程 |
E185647
|
entity |
| Predicate | 定位 |
P80176
|
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: [211工程, 定位, 服务国家战略需求的高等教育工程]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 定位 Context triple: [211工程, 定位, 服务国家战略需求的高等教育工程]
-
A.
positionEstablishedIn
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
-
B.
locationComponent
Indicates that one entity is a constituent or sub-part of a larger location defined by another entity.
-
C.
locationFocus
Indicates that the primary or most relevant location associated with an entity, event, or relation is being specified or emphasized.
-
D.
positionEstablishedFor
Indicates that a specific role or job position has been formally created or set up for a particular entity or purpose.
-
E.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
- F. None of above. chosen
Provenance (4 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_69ca829a2cfc819083d591d58ec04075 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c2b543c81909b82bc478d579e0b |
completed | March 31, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:15 p.m.