Triple
T34851799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BIO International Convention |
E1004617
|
entity |
| Predicate | hasRotatingHostCities |
P13981
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [BIO International Convention, hasRotatingHostCities, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRotatingHostCities Context triple: [BIO International Convention, hasRotatingHostCities, true]
-
A.
rotatingHostCity
chosen
Indicates that the role of host city changes periodically among different cities according to a rotation schedule.
-
B.
tournamentHostCities
Indicates the cities that serve as hosts for a given tournament.
-
C.
usesMultipleHostCities
Indicates that an event or activity is held across more than one host city rather than being confined to a single location.
-
D.
hostCityPreviouslyHosted
Indicates that the city currently hosting an event has also hosted that same event in one or more previous editions.
-
E.
hasCoHostCity
Indicates that an event is jointly hosted or organized by the specified city alongside one or more other cities.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: May 3, 2026, 4 p.m.