Triple
T37968964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 刘步蟾 |
E947225
|
entity |
| Predicate | roleInFirstSinoJapaneseWar |
P204073
|
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: [刘步蟾, roleInFirstSinoJapaneseWar, 北洋舰队主力战舰定远舰舰长]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFirstSinoJapaneseWar Context triple: [刘步蟾, roleInFirstSinoJapaneseWar, 北洋舰队主力战舰定远舰舰长]
-
A.
roleDuringSecondSinoJapaneseWar
Indicates the specific role, position, or function an entity held or performed during the Second Sino-Japanese War.
-
B.
roleAtBattleOfYaluRiver
Indicates the specific role, position, or function an entity held or performed during the Battle of the Yalu River.
-
C.
roleInKoreanWar
Indicates the specific function, position, or involvement an entity had during the Korean War.
-
D.
roleInManchuria
Indicates that an entity holds or held a specific role, position, or function in the context of Manchuria.
-
E.
ChineseAllyInKoreanWar
Indicates that one entity was an ally of China during the Korean 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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a03173dd4988190a38175b63cba9f09 |
completed | May 12, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_6a031700ade88190afd217d5966b03b4 |
completed | May 12, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_6a03173d2a0c8190be051944693e3914 |
completed | May 12, 2026, 12:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.