Triple
T6965551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milan Fashion Week |
E161477
|
entity |
| Predicate | hostCityRole |
P8234
|
FINISHED |
| Object | fashion capital |
—
|
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: fashion capital | Statement: [Milan Fashion Week, hostCityRole, fashion capital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostCityRole Context triple: [Milan Fashion Week, hostCityRole, fashion capital]
-
A.
hostCityInstanceOf
Indicates that a specific host city is an instance of a particular class or type of host city (e.g., Olympic host city, World Cup host city).
-
B.
hasCityRole
chosen
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
C.
hostCityRegion
Indicates the city or broader region that serves as the host location for a specified event or entity.
-
D.
rotatingHostCity
Indicates that the role of host city changes periodically among different cities according to a rotation schedule.
-
E.
hostCityResponsibility
Indicates the obligations or duties that a designated host city has in relation to an event, activity, or arrangement.
- 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db1049e0819097099a0e9d15f787 |
completed | March 27, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.