Triple
T24892748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flers-lez-Lille |
E623047
|
entity |
| Predicate | formedNewCommune |
P101485
|
FINISHED |
| Object | Villeneuve-d’Ascq |
—
|
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: Villeneuve-d’Ascq | Statement: [Flers-lez-Lille, formedNewCommune, Villeneuve-d’Ascq]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedNewCommune Context triple: [Flers-lez-Lille, formedNewCommune, Villeneuve-d’Ascq]
-
A.
formedMunicipalityWith
chosen
Indicates that two or more entities combined or were merged to create a single municipality.
-
B.
formsBiStateCommunityWith
Indicates that two entities jointly constitute or participate in a shared bi-state community spanning both of their jurisdictions.
-
C.
hasCommune
Indicates a relationship where an entity is associated with, belongs to, or is located within a specific commune (municipal administrative unit).
-
D.
formedMunicipalityOn
Indicates that a new municipality was officially created or established on a specific date.
-
E.
reconstitutedAsMunicipality
Indicates that an entity which previously lost or changed its municipal status has been formally re-established or reorganized as a municipality.
- 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 18, 2026, 5:26 a.m.