Triple
T25734859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond Football Club |
E645346
|
entity |
| Predicate | guernseyColor |
P159197
|
FINISHED |
| Object | black with yellow sash |
—
|
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 with yellow sash | Statement: [Richmond Football Club, guernseyColor, black with yellow sash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guernseyColor Context triple: [Richmond Football Club, guernseyColor, black with yellow sash]
-
A.
capeColor
Indicates the color attribute associated with a cape worn or possessed by an entity.
-
B.
hackleColor
Indicates the color characteristic of an entity’s hackles (the raised hairs or feathers along the neck/back).
-
C.
coatColorSymbol
Indicates the symbolic or coded representation used to denote an entity’s coat color in a standardized form.
-
D.
ensignColor
Indicates the color or colors displayed on an entity’s ensign (flag or banner).
-
E.
heraldicColor
Indicates that one entity specifies or bears a particular heraldic color in a coat of arms or related heraldic context.
- F. None of above. chosen
Provenance (4 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fcbead288190ad04ffa3c4d463be |
completed | May 2, 2026, 1:31 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 11:22 p.m.