Triple
T33347802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julian Savea |
E853846
|
entity |
| Predicate | wasTopTryScorerIn |
P57794
|
FINISHED |
| Object | 2015 Rugby World Cup |
—
|
NE NERFINISHED |
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: 2015 Rugby World Cup | Statement: [Julian Savea, wasTopTryScorerIn, 2015 Rugby World Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasTopTryScorerIn Context triple: [Julian Savea, wasTopTryScorerIn, 2015 Rugby World Cup]
-
A.
isAmongTopScorers
Indicates that an entity ranks within the highest-performing group based on a scoring or evaluation metric.
-
B.
topScorer
Indicates that the subject is the individual with the highest score among a specified group or in a particular context.
-
C.
isTopScorerTitleOf
Indicates that one entity is the title or designation awarded to the top scorer associated with another entity (such as a competition, season, or team).
-
D.
mostTriesScoredByPlayer
chosen
Indicates that the referenced player holds the record for scoring the highest number of tries, typically within a specified competition, season, or context.
-
E.
goalScorerIn
Indicates that an entity is the player who scored a goal in a particular match or event.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.