Triple

T4859752
Position Surface form Disambiguated ID Type / Status
Subject Tosa-class battleship E108627 entity
Predicate displacementPlanned P57907 FINISHED
Object approximately 39,000 tons standard 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: approximately 39,000 tons standard | Statement: [Tosa-class battleship, displacementPlanned, approximately 39,000 tons standard]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: displacementPlanned
Context triple: [Tosa-class battleship, displacementPlanned, approximately 39,000 tons standard]
  • A. plannedDisplacement
    Indicates a deliberate, pre-arranged movement or relocation of an entity from one place or state to another.
  • B. displacement
    Indicates a change in an entity’s position from one location to another, typically specifying both direction and magnitude of that movement.
  • C. designedDisplacement chosen
    Indicates the intended or specified amount of displacement (such as volume or weight moved) that something is engineered or planned to produce or accommodate.
  • D. plannedLocation
    Indicates the intended or scheduled location where an entity is expected to be or an event is planned to occur.
  • E. displacementCategory
    Indicates the type or classification of a displacement event or condition associated with an entity.
  • 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_69bd440b965081908b0557721cae6338 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6d5c92148190a314707bdd3ff30f completed March 20, 2026, 3:53 p.m.
PD Predicate disambiguation batch_69bd6c27334481909ba8ac80854f7d8e completed March 20, 2026, 3:47 p.m.
Created at: March 20, 2026, 1:26 p.m.