Triple
T454838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Unity Day |
E7210
|
entity |
| Predicate | rotatingHostCity |
P13981
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [German Unity Day, rotatingHostCity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotatingHostCity Context triple: [German Unity Day, rotatingHostCity, yes]
-
A.
hasCoHostCity
Indicates that an event is jointly hosted or organized by the specified city alongside one or more other cities.
-
B.
hasHostCity
Indicates that a particular event, organization, or activity is located in or officially hosted by a specific city.
-
C.
cityHostedAgain
Indicates that a city has hosted a particular event on more than one occasion, including the current instance.
-
D.
hostCityBidWinner
Indicates that a particular city has been selected as the winning bidder to host a specific event or competition.
-
E.
hostCitySelectionLocation
Indicates the location where the selection of a host city takes place.
- F. None of above. chosen
Provenance (4 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef87cc7c8190a0fec933457821e2 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede4de008190b5a6c159e741522e |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeeb85f881909580a6a86332b4a5 |
completed | Feb. 28, 2026, 1:34 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.