Triple

T28874596
Position Surface form Disambiguated ID Type / Status
Subject Royal Malaysian Navy E732231 entity
Predicate hasComponent P35 FINISHED
Object Eastern Fleet
Eastern Fleet is a major operational command of the Royal Malaysian Navy responsible for maritime security and naval operations in Malaysia’s eastern maritime regions.
E1839295 NE 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: Eastern Fleet | Statement: [Royal Malaysian Navy, hasComponent, Eastern Fleet]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Eastern Fleet
Triple: [Royal Malaysian Navy, hasComponent, Eastern Fleet]
Generated description
Eastern Fleet is a major operational command of the Royal Malaysian Navy responsible for maritime security and naval operations in Malaysia’s eastern maritime regions.

Provenance (5 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_69f05b06807c81909b4bbd4c20403a2b completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69f65a4a48888190b3c1bc721712ae71 completed May 2, 2026, 8:10 p.m.
NED1 Entity disambiguation (via context triple) batch_6a24d3fca02c81908d1a28feb2fdd480 completed June 7, 2026, 2:14 a.m.
NEDg Description generation batch_6a24d822508c819088e198c41c40470f completed June 7, 2026, 2:32 a.m.
NED2 Entity disambiguation (via description) batch_6a24dc337048819086938831cc584389 completed June 7, 2026, 2:49 a.m.
Created at: April 28, 2026, 7:36 a.m.