Triple
T18844283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharks Sevens |
E460874
|
entity |
| Predicate | jerseyAssociation |
P112173
|
FINISHED |
| Object | black and white colours of the Sharks |
—
|
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: black and white colours of the Sharks | Statement: [Sharks Sevens, jerseyAssociation, black and white colours of the Sharks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jerseyAssociation Context triple: [Sharks Sevens, jerseyAssociation, black and white colours of the Sharks]
-
A.
jersey
Indicates that one entity is the jersey (sports uniform top) associated with, worn by, or representing another entity.
-
B.
jerseyHonor
Indicates that an entity has been honored by having its jersey formally recognized, typically through retirement or special commemoration.
-
C.
jerseySignificance
Indicates the importance, meaning, or symbolic value associated with a particular jersey in a given context.
-
D.
jerseyDescription
chosen
Indicates that a textual description is provided for a particular jersey, such as its appearance, style, or distinguishing features.
-
E.
jerseyName
Indicates the name or label that appears on an entity’s 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8ed944c81908592f0c34e5727a0 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.