Triple

T4081595
Position Surface form Disambiguated ID Type / Status
Subject Five-Power Treaty E87487 entity
Predicate limitedConstructionOf P1050 FINISHED
Object battleships 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: battleships | Statement: [Five-Power Treaty, limitedConstructionOf, battleships]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: limitedConstructionOf
Context triple: [Five-Power Treaty, limitedConstructionOf, battleships]
  • A. ledToConstructionOf
    Indicates that one entity caused, initiated, or was the primary reason for the construction or creation of another entity.
  • B. restriction chosen
    Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
  • C. hasConstruction
    Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
  • D. designedToConstrain
    Indicates that one entity is intentionally created or configured to limit, restrict, or control the behavior, range, or properties of another entity.
  • E. restrictedRight
    Indicates that an entity’s ability to exercise a particular right is limited, constrained, or subject to specific conditions or prohibitions.
  • 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_69aed9435cf48190ad1da737c962d19d completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefc77dab481909bcf197daf2def59 completed March 9, 2026, 4:59 p.m.
PD Predicate disambiguation batch_69aef9082c2081908474f082a49bebc8 completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:39 p.m.