Triple
T16983804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian cruiser Varyag |
E412008
|
entity |
| Predicate | statusAtBattle |
P125389
|
FINISHED |
| Object | outnumbered and outgunned by Japanese squadron |
—
|
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: outnumbered and outgunned by Japanese squadron | Statement: [Russian cruiser Varyag, statusAtBattle, outnumbered and outgunned by Japanese squadron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAtBattle Context triple: [Russian cruiser Varyag, statusAtBattle, outnumbered and outgunned by Japanese squadron]
-
A.
statusDuringBattle
chosen
Indicates the condition or state an entity has while a specific battle or combat event is taking place.
-
B.
statusAfterBattle
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
-
C.
statusAfterAttack
Indicates the resulting condition or state of an entity after an attack has occurred.
-
D.
allyInBattle
Indicates that two or more entities cooperate on the same side as partners during a specific battle or combat situation.
-
E.
positionInBattle
Indicates the specific role or placement an entity occupies within the formation or structure of a battle.
- F. None of above.
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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d18a0bf881908c449f499eb86495 |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.