Triple
T23812882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Host City Contract |
E589906
|
entity |
| Predicate | isSignedAfter |
P20698
|
FINISHED |
| Object | selection of the host city by the IOC Session |
—
|
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: selection of the host city by the IOC Session | Statement: [Host City Contract, isSignedAfter, selection of the host city by the IOC Session]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSignedAfter Context triple: [Host City Contract, isSignedAfter, selection of the host city by the IOC Session]
-
A.
isSigned
Indicates that an entity has been formally endorsed or authenticated through a signature or signing action.
-
B.
signedAfter
chosen
Indicates that one signing event occurred later in time than another signing event.
-
C.
signedBefore
Indicates that one signing event occurred earlier in time than another signing event.
-
D.
alsoSignedWith
Indicates that an entity signed or endorsed something together with another specified entity, as part of the same signing action or agreement.
-
E.
isSignedAlong
Indicates that an entity has signed or endorsed something in conjunction with another specified 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7a911f481909c8a98a5aec72b4b |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:57 p.m.