Triple
T29778489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Going for Gold |
E755445
|
entity |
| Predicate | contestantScope |
P24020
|
FINISHED |
| Object | various European countries |
—
|
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: various European countries | Statement: [Going for Gold, contestantScope, various European countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contestantScope Context triple: [Going for Gold, contestantScope, various European countries]
-
A.
contestantOn
Indicates that one entity participates as a competitor in a contest, show, or competition associated with another entity.
-
B.
participantScope
chosen
Indicates the extent, range, or set of participants that are involved in or affected by a given relationship or action.
-
C.
featuresContestantSelectionBy
Indicates that something includes or presents a contestant selection process carried out by a specified agent or entity.
-
D.
featuresContestantsFrom
Indicates that something, typically a show or event, includes contestants originating from a specified source or group.
-
E.
featuresContestants
Indicates that something (such as an event, show, or competition) includes or presents certain individuals as contestants.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 28, 2026, 8:48 p.m.