Triple
T16751013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stade Bollaert-Delelis |
E407076
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object |
Félix Bollaert
Félix Bollaert was a French industrialist and director of the Compagnie des Mines de Lens, in whose honor the main football stadium in Lens was named.
|
E1929857
|
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: Félix Bollaert | Statement: [Stade Bollaert-Delelis, namedAfter, Félix Bollaert]
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: Félix Bollaert Triple: [Stade Bollaert-Delelis, namedAfter, Félix Bollaert]
Generated description
Félix Bollaert was a French industrialist and director of the Compagnie des Mines de Lens, in whose honor the main football stadium in Lens was named.
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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa271de48190b4a535408aeef734 |
completed | April 18, 2026, 3:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2898afbcac819090a462e0ddb1dc56 |
completed | June 9, 2026, 10:50 p.m. |
| NEDg | Description generation | batch_6a289987c9988190a355050ae3113a08 |
completed | June 9, 2026, 10:53 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a289d68dafc8190a4624b6bc4f54b9c |
completed | June 9, 2026, 11:10 p.m. |
Created at: April 10, 2026, 5:21 a.m.