Triple
T38196545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaumont Volley-Ball 52 |
E1005629
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object |
Chaumont VB 52
Chaumont VB 52 is a professional French men's volleyball club competing in the country's top leagues and European competitions.
|
E2260216
|
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: Chaumont VB 52 | Statement: [Chaumont Volley-Ball 52, shortName, Chaumont VB 52]
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: Chaumont VB 52 Triple: [Chaumont Volley-Ball 52, shortName, Chaumont VB 52]
Generated description
Chaumont VB 52 is a professional French men's volleyball club competing in the country's top leagues and European competitions.
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_69f76dbd22f48190940318cea061e8bb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcb11b9268819094866720251b927a |
completed | May 7, 2026, 3:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a417b43c908819094f774b4384ae16a |
completed | June 28, 2026, 7:51 p.m. |
| NEDg | Description generation | batch_6a417fbe98e88190876febaf49474317 |
completed | June 28, 2026, 8:10 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a41803ffc70819082a30a05c2b95f63 |
completed | June 28, 2026, 8:12 p.m. |
Created at: May 3, 2026, 4:29 p.m.