Triple
T35859874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tayside Police |
E1036915
|
entity |
| Predicate | badgeCaption |
P168477
|
FINISHED |
| Object | Tayside Police crest and motto |
—
|
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: Tayside Police crest and motto | Statement: [Tayside Police, badgeCaption, Tayside Police crest and motto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: badgeCaption Context triple: [Tayside Police, badgeCaption, Tayside Police crest and motto]
-
A.
badgeText
Indicates that a visual badge or label is associated with an entity, displaying specific text content.
-
B.
badgeTranslation
Indicates that one badge serves as a translation or localized version of another badge.
-
C.
badge
Indicates that one entity confers, displays, or is associated with a symbolic mark or emblem representing status, achievement, role, or affiliation in relation to another entity.
-
D.
badgeCategory
Indicates the classification or type group to which a particular badge belongs.
-
E.
badgeDescription
chosen
Indicates the textual explanation or details that describe what a particular badge represents or signifies.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.