Triple

T10617590
Position Surface form Disambiguated ID Type / Status
Subject Japanese cruiser Yoshino E276161 entity
Predicate roleAtBattleOfYaluRiver P94997 FINISHED
Object served as a fast wing ship in the Japanese line 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: served as a fast wing ship in the Japanese line | Statement: [Japanese cruiser Yoshino, roleAtBattleOfYaluRiver, served as a fast wing ship in the Japanese line]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleAtBattleOfYaluRiver
Context triple: [Japanese cruiser Yoshino, roleAtBattleOfYaluRiver, served as a fast wing ship in the Japanese line]
  • A. roleDuringSecondSinoJapaneseWar
    Indicates the specific role, position, or function an entity held or performed during the Second Sino-Japanese War.
  • B. roleInKoreanWar
    Indicates the specific function, position, or involvement an entity had during the Korean War.
  • C. roleInManchuria
    Indicates that an entity holds or held a specific role, position, or function in the context of Manchuria.
  • D. roleAtBattleOfIquique
    Indicates the specific role or function an entity held during the Battle of Iquique.
  • E. sideInBattleOfYiling
    Indicates that an entity participated as a side or faction in the Battle of Yiling.
  • 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_69d6aaf948d88190806cc3a8c47a3fb2 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d6df6e2df4819099a19b59d90d0dd1 completed April 8, 2026, 11:06 p.m.
PD Predicate disambiguation batch_69d6dd7a223c8190854409d76368f3e8 completed April 8, 2026, 10:58 p.m.
PDg Predicate description generation batch_69d6df463ea8819091d6683e476b4f21 completed April 8, 2026, 11:05 p.m.
Created at: April 8, 2026, 7:33 p.m.