Triple
T2212664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beiyang Fleet |
E50951
|
entity |
| Predicate | statusBeforeWar |
P36829
|
FINISHED |
| Object | one of the most powerful navies in East Asia |
—
|
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: one of the most powerful navies in East Asia | Statement: [Beiyang Fleet, statusBeforeWar, one of the most powerful navies in East Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusBeforeWar Context triple: [Beiyang Fleet, statusBeforeWar, one of the most powerful navies in East Asia]
-
A.
statusDuringWar
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
B.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
C.
enemyDuringWar
Indicates that one entity is an enemy of another specifically in the context of a particular war or armed conflict.
-
D.
usedAfterWar
Indicates that an entity came into use only after a specific war or conflict had ended.
-
E.
statusAfterColdWar
Indicates the condition or standing of an entity in the period following the end of the Cold 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfee6ae48190825ca792e8f99946 |
completed | March 7, 2026, 6:04 a.m. |
| PD | Predicate disambiguation | batch_69abbdaa26d48190860c33fd464c4845 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf0c2b8881908553eed5be17a9c2 |
completed | March 7, 2026, 6 a.m. |
Created at: March 4, 2026, 7:46 p.m.