Triple
T36366188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lumières de Noël de Montbéliard |
E895630
|
entity |
| Predicate | organisateurPrincipal |
P44627
|
FINISHED |
| Object | ville de Montbéliard |
—
|
NE NERFINISHED |
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: ville de Montbéliard | Statement: [Lumières de Noël de Montbéliard, organisateurPrincipal, ville de Montbéliard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organisateurPrincipal Context triple: [Lumières de Noël de Montbéliard, organisateurPrincipal, ville de Montbéliard]
-
A.
principalOrganizer
chosen
Indicates that an entity serves as the main or leading organizer responsible for planning or coordinating another entity or event.
-
B.
firstOrganizer
Indicates that an entity serves as the primary or initial organizer in relation to another event, group, or activity.
-
C.
organizerRepresents
Indicates that an organizer acts on behalf of, or serves as the representative of, another entity in a given context.
-
D.
lastOrganizer
Indicates that one entity is the most recent or final organizer associated with another entity or event.
-
E.
organizadoPor
Indicates that something is arranged, managed, or coordinated by a particular agent or entity.
- F. None of above.
Provenance (3 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:10 p.m.