Triple
T29258196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 後周 |
E741761
|
entity |
| Predicate | militarySystemReform |
P92051
|
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: [後周, militarySystemReform, 整編禁軍]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militarySystemReform Context triple: [後周, militarySystemReform, 整編禁軍]
-
A.
militarySystem
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
-
B.
militaryPolicy
Indicates a relationship where an entity defines, adopts, or is governed by rules, strategies, or doctrines concerning military organization, operations, or conduct.
-
C.
involvesMilitaryChange
chosen
Indicates that the situation or event includes a modification, reorganization, or shift in military forces, structures, capabilities, or operations.
-
D.
militaryIssue
Indicates that one entity formally provides or distributes military-related items, orders, or directives to another entity.
-
E.
militaryDoctrine
Indicates that one entity embodies, follows, or defines the strategic military principles, tactics, and operational guidelines used by 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 12:39 p.m.