Triple
T21541784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guinness World Record for the largest number of noble titles |
E531508
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Guinness World Record category |
C6519
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Guinness World Record category Context triple: [Guinness World Record for the largest number of noble titles, instanceOf, Guinness World Record category]
-
A.
record holder
A record holder is an entity (person, team, or organization) that has achieved and officially maintains the highest or most extreme performance in a specific measurable category or event.
-
B.
category of sports
A category of sports is a conceptual grouping that classifies individual sports based on shared characteristics such as objectives, rules, required skills, or equipment.
-
C.
Golden Goblet Award category
A Golden Goblet Award category represents a specific area of achievement (such as acting, directing, or technical craft) in which films or individuals are nominated and judged at the Shanghai International Film Festival.
-
D.
recognition category
chosen
A recognition category is a mental grouping of stimuli or objects that are treated as equivalent for the purpose of identifying, classifying, or responding to them.
-
E.
participation category
A participation category classifies the level, type, or role of involvement that individuals or entities have within an activity, event, or system.
- F. None of above.
Provenance (1 batch)
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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:28 p.m.