Triple

T7398062
Position Surface form Disambiguated ID Type / Status
Subject Johor-Riau-Lingga Sultanate E170673 entity
Predicate seaPower P21383 FINISHED
Object Malay maritime polity 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: Malay maritime polity | Statement: [Johor-Riau-Lingga Sultanate, seaPower, Malay maritime polity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: seaPower
Context triple: [Johor-Riau-Lingga Sultanate, seaPower, Malay maritime polity]
  • A. navalPowerStatus chosen
    Indicates the relative strength, capability, or strategic standing of an entity’s naval forces compared to others or to defined benchmarks.
  • B. navalFleet
    Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
  • C. hasNavalComponent
    Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
  • D. embarkedForcesCapacity
    Indicates the maximum number of forces (e.g., troops or personnel) that can be embarked or carried by a given platform or unit.
  • E. navalFeatures
    Indicates that something possesses characteristics, components, or attributes specifically associated with naval or maritime contexts.
  • 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_69c68a5f04188190ac266569c9280347 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f24c1c208190a3d11e816888760d completed March 27, 2026, 9:10 p.m.
PD Predicate disambiguation batch_69c6f0323b2c819098ab72c33e6d8534 completed March 27, 2026, 9:01 p.m.
Created at: March 27, 2026, 3:09 p.m.