Triple

T26916549
Position Surface form Disambiguated ID Type / Status
Subject France Antarctique E677531 entity
Predicate hasCapital P204 FINISHED
Object Fort Coligny
Fort Coligny was a short-lived 16th-century French colonial stronghold in present-day Rio de Janeiro, established as the main settlement of the France Antarctique colony.
E1746310 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: Fort Coligny | Statement: [France Antarctique, hasCapital, Fort Coligny]
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: Fort Coligny
Triple: [France Antarctique, hasCapital, Fort Coligny]
Generated description
Fort Coligny was a short-lived 16th-century French colonial stronghold in present-day Rio de Janeiro, established as the main settlement of the France Antarctique colony.

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_69eee9bdebc48190ba90a12a63e09c73 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f61fdec59081909f6d49aca3e8961c completed May 2, 2026, 4:01 p.m.
NED1 Entity disambiguation (via context triple) batch_6a121eb4f5208190939fe86ba18a47ab completed May 23, 2026, 9:40 p.m.
NEDg Description generation batch_6a121f5c372481909cfd4c5ebc39f5ea completed May 23, 2026, 9:42 p.m.
NED2 Entity disambiguation (via description) batch_6a122004aadc819084dbaa834408a0bc completed May 23, 2026, 9:45 p.m.
Created at: April 27, 2026, 6:04 a.m.