Triple
T35084595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | communauté d’agglomération du Saint-Quentinois |
E1012540
|
entity |
| Predicate | villeCentre |
P179414
|
FINISHED |
| Object | Saint-Quentin |
—
|
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: Saint-Quentin | Statement: [communauté d’agglomération du Saint-Quentinois, villeCentre, Saint-Quentin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: villeCentre Context triple: [communauté d’agglomération du Saint-Quentinois, villeCentre, Saint-Quentin]
-
A.
municipalCentre
Indicates that a location functions as the primary administrative or civic center for a municipality.
-
B.
hasMonumentInCenter
Indicates that a place or area has a monument located at its central point or main focal area.
-
C.
cityCentreAccess
Indicates whether an entity has access to, or is reachable within, the central area of a city.
-
D.
hasCityCentreLocation
Indicates that something is located in, or directly associated with, the central area of a city.
-
E.
isTownCenterOf
chosen
Indicates that a location functions as the central, primary area or hub of a specified town.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.