Triple
T29778496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Going for Gold |
E755445
|
entity |
| Predicate | languageOfContestants |
P198138
|
FINISHED |
| Object | English as common language |
—
|
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: English as common language | Statement: [Going for Gold, languageOfContestants, English as common language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfContestants Context triple: [Going for Gold, languageOfContestants, English as common language]
-
A.
languageOfCompetition
Indicates the language in which a competition is conducted or officially presented.
-
B.
languageOfGame
Indicates that a particular language is used as the primary or official language for a given game.
-
C.
languageOfSurroundingCountry
Indicates that a language is the primary or commonly used language in the country surrounding a given place or region.
-
D.
languageOfSurroundingCulture
Indicates that one entity is the language predominantly used or characteristic of the surrounding culture associated with another entity.
-
E.
languageOfEvent
Indicates the language in which an event is conducted, presented, or communicated.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69fecd091abc8190872974de731a80fa |
completed | May 9, 2026, 5:58 a.m. |
Created at: April 28, 2026, 8:48 p.m.