Triple
T10671269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Country |
E251491
|
entity |
| Predicate | hasRugbyTradition |
P19423
|
FINISHED |
| Object | strong |
—
|
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: strong | Statement: [King Country, hasRugbyTradition, strong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRugbyTradition Context triple: [King Country, hasRugbyTradition, strong]
-
A.
homeCountryRugbyUnion
Indicates the country that serves as the primary national rugby union affiliation or base for an entity.
-
B.
hasWinningTradition
Indicates that an entity (such as a team or organization) is characterized by a consistent history of success or victories in its competitive activities.
-
C.
hasTraditionIn
chosen
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
-
D.
RugbyWorldCupTitles
Indicates the number of Rugby World Cup championship titles an entity (typically a national team) has won.
-
E.
isInCountryRugbyLeagueSystem
Indicates that a rugby league team, club, or competition operates within and is governed by the league structure of a specific country.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6f8648a248190a3bd284c569152e4 |
completed | April 9, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:09 p.m.