Triple

T26595963
Position Surface form Disambiguated ID Type / Status
Subject Pulau Meja E667490 entity
Predicate accessedFrom P1985 FINISHED
Object Riung harbor
Riung harbor is a small coastal port in Riung, Flores, Indonesia, serving as the main departure point for boat trips to nearby islands such as Pulau Meja in the Riung 17 Islands Marine Park.
E1730907 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: Riung harbor | Statement: [Pulau Meja, accessedFrom, Riung harbor]
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: Riung harbor
Triple: [Pulau Meja, accessedFrom, Riung harbor]
Generated description
Riung harbor is a small coastal port in Riung, Flores, Indonesia, serving as the main departure point for boat trips to nearby islands such as Pulau Meja in the Riung 17 Islands Marine Park.

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_69ee9cfc385081909ac9ae178030a06e completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f61529a5748190896ba1a1d19aeaa1 completed May 2, 2026, 3:15 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11c83cfe488190aeae3615cde2071a completed May 23, 2026, 3:31 p.m.
NEDg Description generation batch_6a11c8d922608190b7b1d32a42e986d5 completed May 23, 2026, 3:33 p.m.
NED2 Entity disambiguation (via description) batch_6a11c99a6eec81909171f7d03a056fc8 completed May 23, 2026, 3:36 p.m.
Created at: April 27, 2026, 2:10 a.m.