Triple

T37414295
Position Surface form Disambiguated ID Type / Status
Subject Armed Forces of the Dominican Republic E929656 entity
Predicate hasHeadquartersLocation P62 FINISHED
Object Santo Domingo
Santo Domingo is the capital and largest city of the Dominican Republic, serving as its political, economic, and cultural center.
E839205 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: Santo Domingo | Statement: [Armed Forces of the Dominican Republic, hasHeadquartersLocation, Santo Domingo]
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: Santo Domingo
Triple: [Armed Forces of the Dominican Republic, hasHeadquartersLocation, Santo Domingo]
Generated description
Santo Domingo is the capital and largest city of the Dominican Republic, serving as its political, economic, and cultural center.

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_69f76ebde49481908566cd96b37ccc84 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb8d86ca8c8190aa8fe72272f45c29 completed May 6, 2026, 6:50 p.m.
NED1 Entity disambiguation (via context triple) batch_6a408c264c508190a01a166221ccc07f completed June 28, 2026, 2:51 a.m.
NEDg Description generation batch_6a408d599f448190aa59dc8ee1ccfbe8 completed June 28, 2026, 2:56 a.m.
NED2 Entity disambiguation (via description) batch_6a408e77450c81909759a071e7ec31fa completed June 28, 2026, 3:01 a.m.
Created at: May 3, 2026, 4:16 p.m.