Triple

T34590498
Position Surface form Disambiguated ID Type / Status
Subject Port system of Indonesia E888167 entity
Predicate includesPort P65472 FINISHED
Object Port of Kupang
The Port of Kupang is a key maritime gateway and commercial harbor serving the city of Kupang and the surrounding region in East Nusa Tenggara, Indonesia.
E2113906 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: Port of Kupang | Statement: [Port system of Indonesia, includesPort, Port of Kupang]
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: Port of Kupang
Triple: [Port system of Indonesia, includesPort, Port of Kupang]
Generated description
The Port of Kupang is a key maritime gateway and commercial harbor serving the city of Kupang and the surrounding region in East Nusa Tenggara, Indonesia.

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_69f349d3bfcc81909874c99e646fb3ea completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f720cc1bfc8190a16118e3af8e9316 completed May 3, 2026, 10:17 a.m.
NED1 Entity disambiguation (via context triple) batch_6a376f8e1bb08190a4f653170d5cc1bb completed June 21, 2026, 4:58 a.m.
NEDg Description generation batch_6a37715f5fe48190b3e55077244032ce completed June 21, 2026, 5:06 a.m.
NED2 Entity disambiguation (via description) batch_6a37722ef0b48190b44093b10978145a completed June 21, 2026, 5:10 a.m.
Created at: May 1, 2026, 2:03 a.m.