Triple
T4545329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Ontario |
E110031
|
entity |
| Predicate | hasSupporterSinister |
P57637
|
FINISHED |
| Object | deer |
—
|
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: deer | Statement: [Coat of arms of Ontario, hasSupporterSinister, deer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupporterSinister Context triple: [Coat of arms of Ontario, hasSupporterSinister, deer]
-
A.
hasSupporter
Indicates that one entity supports, endorses, or backs another entity.
-
B.
hasSupporterGroup
Indicates that an entity is associated with a group of supporters that backs, promotes, or advocates for it.
-
C.
usesSupporter
Indicates that one entity makes use of another entity that serves as its supporter, helper, or backing resource in performing an action or fulfilling a role.
-
D.
hasSupporterNickname
Indicates that an entity is associated with a nickname or informal name used specifically by its supporters or fans.
-
E.
hasSupportersSection
Indicates that something includes a dedicated section or area specifically intended for its supporters.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57d62a8481909d5d803a582c76a1 |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:05 p.m.