Triple
T8942916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Civil War |
E212946
|
entity |
| Predicate | secondPhaseEndDate |
P8970
|
FINISHED |
| Object | 1949 |
—
|
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: 1949 | Statement: [Chinese Civil War, secondPhaseEndDate, 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondPhaseEndDate Context triple: [Chinese Civil War, secondPhaseEndDate, 1949]
-
A.
secondRoundEndDate
Indicates the date on which the second round of an event, process, or activity concludes.
-
B.
secondPhase
chosen
Indicates that an entity is in, or has progressed to, the second phase or stage of a multi-phase process or sequence.
-
C.
secondTermEnd
Indicates that the referenced time or event marks the conclusion of the second term in a sequence of terms.
-
D.
secondReachedDate
Indicates the date on which the second specified event, state, or condition is reached or occurs.
-
E.
secondRoundDate
Indicates the date on which the second round of an event, process, or sequence is scheduled or occurs.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66d93978819084b1a5c7c5dd2372 |
completed | April 1, 2026, 12:29 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:58 p.m.