Triple
T7984176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 211工程 |
E185647
|
entity |
| Predicate | 实施主体 |
P52937
|
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.
subjectOfExecution
Indicates that one entity is the object or target upon which an execution (carrying out of a death sentence) is performed by another entity.
-
B.
mainImplementer
chosen
Indicates that an entity is the primary party responsible for carrying out, developing, or executing a specified action, project, or implementation.
-
C.
subjectOfOperation
Indicates that an entity is the primary focus, target, or object upon which an operation or procedure is performed.
-
D.
isConductedBy
Indicates that an event, activity, or process is carried out, organized, or overseen by a particular agent or entity.
-
E.
implementsAct
Indicates that one entity carries out, executes, or puts into effect a specified act, plan, or directive associated with 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_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. |
Created at: March 30, 2026, 5:15 p.m.