Triple
T2395942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yang Hucheng |
E47650
|
entity |
| Predicate | goalInXiAnIncident |
P32840
|
FINISHED |
| Object | end Chinese civil war to resist Japan |
—
|
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: end Chinese civil war to resist Japan | Statement: [Yang Hucheng, goalInXiAnIncident, end Chinese civil war to resist Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalInXiAnIncident Context triple: [Yang Hucheng, goalInXiAnIncident, end Chinese civil war to resist Japan]
-
A.
laterGoal
Indicates that one goal occurs or is intended to be achieved after another goal in time.
-
B.
statedAsGoalFor
chosen
Indicates that something has been explicitly declared or identified as a goal for a particular entity or context.
-
C.
civilianTarget
Indicates that the action or operation is directed at, affects, or designates civilians or civilian objects as the target.
-
D.
AustrianObjective
Indicates that an entity has an objective, goal, or purpose specifically associated with Austria or Austrian context.
-
E.
notableProtectiveIncident
Indicates that a significant event occurred in which one entity protected or defended another in a notable or remarkable way.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc879b1b88190be8d0337d9a17bd0 |
completed | March 7, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69abc5a3825c81909ec6111dfc165453 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.