Triple
T34133817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longpré |
E875508
|
entity |
| Predicate | isSectionOfMunicipality |
P21214
|
FINISHED |
| Object | Wanze |
E295672
|
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: Wanze | Statement: [Longpré, isSectionOfMunicipality, Wanze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSectionOfMunicipality Context triple: [Longpré, isSectionOfMunicipality, Wanze]
-
A.
isPartOfMunicipalityType
Indicates that one administrative unit or area belongs to, or is classified under, a specific type or category of municipality.
-
B.
isInMunicipality
chosen
Indicates that one entity (typically a place or address) is located within the administrative boundaries of a specific municipality.
-
C.
hasMunicipalPart
Indicates that an administrative or territorial entity includes a municipality as one of its constituent parts.
-
D.
isMunicipalSectorOf
Indicates that one entity is a municipal-level subdivision, department, or sector that forms part of the organizational structure of another entity (typically a municipality or local government).
-
E.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
- F. None of above.
Provenance (4 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_69f349aaeef08190a20e72a3fdeb7052 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a375bc4f7108190aefaf59c1a4824d5 |
completed | June 21, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:53 a.m.