Triple
T6610892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | France national rugby league team |
E149232
|
entity |
| Predicate | kitDesign |
P5928
|
FINISHED |
| Object | blue jerseys with tricolour elements |
—
|
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: blue jerseys with tricolour elements | Statement: [France national rugby league team, kitDesign, blue jerseys with tricolour elements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kitDesign Context triple: [France national rugby league team, kitDesign, blue jerseys with tricolour elements]
-
A.
designsFor
Indicates that one entity creates or plans something specifically intended to serve, suit, or be used by another entity.
-
B.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
C.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
D.
helpsDesign
Indicates that one entity assists or contributes to another entity’s design or design process.
-
E.
kitPattern
chosen
Indicates the design or visual pattern featured on a team's kit or uniform.
- 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_69c687ebc680819094caf71faba2efe2 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cf3796d08190a26e988386089447 |
completed | March 27, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69c6acfed25481909cac74c84a9fe088 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:57 p.m.