Triple
T27544468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Administration of Sport of China |
E695322
|
entity |
| Predicate | emblemUsedIn |
P162686
|
FINISHED |
| Object | national sports events in China |
—
|
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: national sports events in China | Statement: [General Administration of Sport of China, emblemUsedIn, national sports events in China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emblemUsedIn Context triple: [General Administration of Sport of China, emblemUsedIn, national sports events in China]
-
A.
emblemUsedBy
Indicates that a particular emblem is adopted or employed by a specific entity as its symbol or identifying mark.
-
B.
emblemName
Indicates that a specified name is the official or recognized title of an emblem.
-
C.
emblematicFor
Indicates that something serves as a representative symbol or characteristic example of something else.
-
D.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
-
E.
emblemBrand
Indicates that one entity serves as the emblem, logo, or symbolic mark representing a particular brand.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f83176c81909a508c03229dc69d |
completed | May 2, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62cd1912c8190ab3f3288442115a4 |
completed | May 2, 2026, 4:56 p.m. |
Created at: April 27, 2026, 1:32 p.m.