Triple
T20005181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFC Richmond |
E494435
|
entity |
| Predicate | hasBanner |
P5950
|
FINISHED |
| Object | Believe sign in locker room |
—
|
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: Believe sign in locker room | Statement: [AFC Richmond, hasBanner, Believe sign in locker room]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBanner Context triple: [AFC Richmond, hasBanner, Believe sign in locker room]
-
A.
usedBanner
Indicates that one entity employed or displayed another entity as a banner in some context or setting.
-
B.
presentedUnderBanner
Indicates that something is displayed or showcased beneath or associated with a specific banner or heading.
-
C.
hasAdvertisingVisual
Indicates that an entity includes, is associated with, or uses a specific visual element or asset for advertising purposes.
-
D.
hasBranding
Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
-
E.
hasSignage
chosen
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a46c748190a141ab5aac6ea250 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.