Triple
T2343814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essonne |
E45084
|
entity |
| Predicate | numberOfArrondissements |
P1679
|
FINISHED |
| Object | 3 |
—
|
LITERAL 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: 3 | Statement: [Essonne, numberOfArrondissements, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfArrondissements Context triple: [Essonne, numberOfArrondissements, 3]
-
A.
hasArrondissement
Indicates a relationship where an administrative unit or locality is associated with, or belongs to, a specific arrondissement.
-
B.
numberOfDistricts
chosen
Indicates the total count of districts associated with a given entity or area.
-
C.
hasNumberOfMunicipalities
Indicates the relationship that specifies how many municipalities are associated with or contained within a given administrative or geographic entity.
-
D.
numberOfRegionalCouncils
Indicates the total count of regional councils associated with a given entity.
-
E.
inseeCode
Indicates the official INSEE (French national statistics institute) code assigned to an entity, typically identifying a specific geographic or administrative unit.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abcade3c808190ab3803538ccbe620 |
completed | March 7, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69abc59616a8819099711834e6f1ccd6 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:52 p.m.