Triple
T10599649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | players touch the "Play Like A Champion Today" sign |
E275707
|
entity |
| Predicate | languageOfSign |
P4196
|
FINISHED |
| Object | English |
—
|
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 | Statement: [players touch the "Play Like A Champion Today" sign, languageOfSign, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfSign Context triple: [players touch the "Play Like A Champion Today" sign, languageOfSign, English]
-
A.
languageOfSignage
chosen
Indicates the language used on signs or written displays associated with an entity.
-
B.
recognizedSignLanguage
Indicates that one entity has correctly identified or understood a sign language used or produced by another entity.
-
C.
usesSignLanguage
Indicates that one entity communicates using sign language with or in relation to another entity.
-
D.
usesFingerspellingSystem
Indicates that one entity employs or applies a particular fingerspelling system in communication or representation.
-
E.
languageSpokenOnScreen
Indicates that a particular language is used in spoken dialogue or audible communication within an on-screen work (such as a film, show, or video).
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4992248190b640d743ccf02c82 |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
Created at: April 8, 2026, 7:30 p.m.