Triple
T5184978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scotiabank became title sponsor in 2005 |
E117007
|
entity |
| Predicate | appliesToAwardType |
P61954
|
FINISHED |
| Object | literary award |
—
|
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: literary award | Statement: [Scotiabank became title sponsor in 2005, appliesToAwardType, literary award]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToAwardType Context triple: [Scotiabank became title sponsor in 2005, appliesToAwardType, literary award]
-
A.
canBeAwardedTo
Indicates that something is eligible to receive or be granted a particular award, honor, or recognition.
-
B.
canBeAwarded
Indicates that an entity is eligible to receive or be granted a particular award, prize, or honor.
-
C.
canAward
Indicates that one entity has the authority or ability to grant an award, honor, or recognition to another entity.
-
D.
hasAwardedEntityType
Indicates that a particular type or category of entity is the recipient of an award or recognition.
-
E.
hasAwardRestriction
Indicates that there is a limitation, condition, or constraint placed on receiving or granting an award.
- 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_69bd44620ff48190bcac01782107a397 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78d6a1388190804dcf568ca92129 |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:46 p.m.