Triple
T23038961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China Lobby |
E573683
|
entity |
| Predicate | positionOnChineseCivilWar |
P150755
|
FINISHED |
| Object | pro-Nationalist |
—
|
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: pro-Nationalist | Statement: [China Lobby, positionOnChineseCivilWar, pro-Nationalist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnChineseCivilWar Context triple: [China Lobby, positionOnChineseCivilWar, pro-Nationalist]
-
A.
survivedChineseCivilWar
Indicates that an entity lived through and remained alive after the events of the Chinese Civil War.
-
B.
roleDuringSecondSinoJapaneseWar
Indicates the specific role, position, or function an entity held or performed during the Second Sino-Japanese War.
-
C.
positionOnChina
Indicates the stance, opinion, or policy that one entity holds regarding China.
-
D.
ChinaPosition
Indicates the stance, policy, or viewpoint officially held or expressed by China regarding a particular issue, event, or entity.
-
E.
survivedSecondSinoJapaneseWar
Indicates that the subject continued to live through and beyond the duration of the Second Sino-Japanese War.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f185121da0819095b523d7d2c923ab |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:53 p.m.