Triple

T26830521
Position Surface form Disambiguated ID Type / Status
Subject Commissioner for Surinam E675487 entity
Predicate appliesToJurisdiction P82 FINISHED
Object English Surinam
English Surinam was the 17th-century English colonial territory on the northern coast of South America in the area of present-day Suriname.
E1744578 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: English Surinam | Statement: [Commissioner for Surinam, appliesToJurisdiction, English Surinam]
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: English Surinam
Triple: [Commissioner for Surinam, appliesToJurisdiction, English Surinam]
Generated description
English Surinam was the 17th-century English colonial territory on the northern coast of South America in the area of present-day Suriname.

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_69eee9b776448190993a60b67fcc9545 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f61adc60c88190924d7b71d52851e8 completed May 2, 2026, 3:40 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12133f1288819080577fff0c3b9681 completed May 23, 2026, 8:51 p.m.
NEDg Description generation batch_6a1215655aac8190b3f1a131550befc2 completed May 23, 2026, 9 p.m.
NED2 Entity disambiguation (via description) batch_6a1216420ef08190b33368157a089c98 completed May 23, 2026, 9:04 p.m.
Created at: April 27, 2026, 5:01 a.m.