Triple
T32009852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angoulême International Comics Festival |
E817368
|
entity |
| Predicate | hostCityKnownFor |
P101499
|
FINISHED |
| Object | city of comics |
—
|
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: city of comics | Statement: [Angoulême International Comics Festival, hostCityKnownFor, city of comics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostCityKnownFor Context triple: [Angoulême International Comics Festival, hostCityKnownFor, city of comics]
-
A.
hostCityLocatedOn
Indicates that the city serving as a host (e.g., of an event) is geographically situated on or along a specified physical feature or area (such as a river, coast, or region).
-
B.
alsoKnownForCity
Indicates that an entity is additionally recognized or notable for its association with a particular city.
-
C.
hostCityOfEvent
Indicates that a city serves as the location where a particular event is held or takes place.
-
D.
homeCityOfNOC
Indicates that a given city is the designated home or base city of a particular National Olympic Committee (NOC).
-
E.
hostCityFeature
chosen
Indicates that a particular feature, attribute, or characteristic is associated with or present in a host city.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:15 a.m.