Triple
T14424647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Vincent-de-Paul, Paris |
E357663
|
entity |
| Predicate | municipalArrondissementNumber |
P47247
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Saint-Vincent-de-Paul, Paris, municipalArrondissementNumber, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalArrondissementNumber Context triple: [Saint-Vincent-de-Paul, Paris, municipalArrondissementNumber, 10]
-
A.
hasArrondissement
Indicates a relationship where an administrative unit or locality is associated with, or belongs to, a specific arrondissement.
-
B.
capitalOfCommune
Indicates that one place serves as the administrative capital or chief town of a given commune.
-
C.
isUrbanAgglomerationMember
Indicates that an entity is part of, or included within, a larger urban agglomeration area.
-
D.
hasMunicipalDistrictNumber
chosen
Indicates that a municipality or local administrative unit is assigned a specific district number within its municipal structure.
-
E.
cityLocatedInDepartment
Indicates that a city is geographically and administratively situated within a specific department.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91123f848190ba3fb18a76c2d24c |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.