Triple
T2212649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beiyang Fleet |
E50951
|
entity |
| Predicate | vessel |
P862
|
FINISHED |
| Object | Zhenyuan |
E248214
|
NE 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: Zhenyuan | Statement: [Beiyang Fleet, vessel, Zhenyuan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zhenyuan Context triple: [Beiyang Fleet, vessel, Zhenyuan]
-
A.
Zhenyuan
chosen
Zhenyuan was a late 19th-century Chinese ironclad battleship of the Beiyang Fleet that played a prominent role in the First Sino-Japanese War.
-
B.
Zhenwu
Zhenwu is a powerful Taoist deity associated with the north, martial protection, and spiritual cultivation, especially revered in Chinese religious and martial traditions.
-
C.
Xue
Xue is a Chinese surname borne by various notable historical and contemporary figures.
-
D.
Xuan
Xuan is a Vietnamese surname commonly used as a family name in Vietnam.
-
E.
Zongren
Zongren is the given name of Li Zongren, a prominent Chinese military commander and political leader of the early to mid-20th century.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfee6ae48190825ca792e8f99946 |
completed | March 7, 2026, 6:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae71b629088190a5228a2f68500bd5 |
completed | March 9, 2026, 7:07 a.m. |
Created at: March 4, 2026, 7:46 p.m.