Triple
T14884381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highlanders |
E350082
|
entity |
| Predicate | jerseyDesignTheme |
P50176
|
FINISHED |
| Object | Highland and southern New Zealand identity |
—
|
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: Highland and southern New Zealand identity | Statement: [Highlanders, jerseyDesignTheme, Highland and southern New Zealand identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jerseyDesignTheme Context triple: [Highlanders, jerseyDesignTheme, Highland and southern New Zealand identity]
-
A.
jerseyDesignInspiredBy
chosen
Indicates that the design of a jersey is based on, influenced by, or derived from another design, theme, or source.
-
B.
jerseyColorThemeOfHost
Indicates that a specified jersey color theme is used by the host team or host entity in an event or competition.
-
C.
jerseyLogo
Indicates that a logo is displayed on or associated with a jersey as part of its design or branding.
-
D.
jersey
Indicates that one entity is the jersey (sports uniform top) associated with, worn by, or representing another entity.
-
E.
primaryJerseyDesign
Indicates the main visual design or pattern used on an entity’s primary jersey 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5f4598081908735e8d7dfce8074 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:56 a.m.