Triple
T2975854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Place Bellecour |
E80393
|
entity |
| Predicate | cityCentreRole |
P8652
|
FINISHED |
| Object | major social hub of Lyon |
—
|
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: major social hub of Lyon | Statement: [Place Bellecour, cityCentreRole, major social hub of Lyon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityCentreRole Context triple: [Place Bellecour, cityCentreRole, major social hub of Lyon]
-
A.
hasCityCentreLocation
Indicates that something is located in, or directly associated with, the central area of a city.
-
B.
urbanRole
chosen
Indicates the function, status, or role that an entity holds within an urban or city context.
-
C.
hasMajorCityRole
Indicates that an entity plays a significant official or functional role in the governance, administration, or key operations of a major city.
-
D.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
E.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad998ad5308190a012ec4940eb46cb |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.