Triple

T24893576
Position Surface form Disambiguated ID Type / Status
Subject canton of Montlouis-sur-Loire E623071 entity
Predicate hasBorderWith P224 FINISHED
Object canton of Amboise
The canton of Amboise is an administrative division in central France centered around the historic town of Amboise in the Indre-et-Loire department.
E1649883 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: canton of Amboise | Statement: [canton of Montlouis-sur-Loire, hasBorderWith, canton of Amboise]
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: canton of Amboise
Triple: [canton of Montlouis-sur-Loire, hasBorderWith, canton of Amboise]
Generated description
The canton of Amboise is an administrative division in central France centered around the historic town of Amboise in the Indre-et-Loire department.

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_69e2fac597708190a922bf39a49ec70a completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f423460acc81909b5a22b9f545b6aa completed May 1, 2026, 3:51 a.m.
NED1 Entity disambiguation (via context triple) batch_6a101c6cbd688190aa3679767ca4e4bd completed May 22, 2026, 9:05 a.m.
NEDg Description generation batch_6a102367c6e0819092a483e21fc5cc6c completed May 22, 2026, 9:35 a.m.
NED2 Entity disambiguation (via description) batch_6a10243c77748190a556b0e26d9a2a1c completed May 22, 2026, 9:39 a.m.
Created at: April 18, 2026, 5:26 a.m.