Triple
T7905021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Achievement Academy Award for Animation Direction |
E183549
|
entity |
| Predicate | regularCategory |
P79693
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Special Achievement Academy Award for Animation Direction, regularCategory, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularCategory Context triple: [Special Achievement Academy Award for Animation Direction, regularCategory, false]
-
A.
uniformCategory
Indicates that two or more entities share the same classification or type within a defined category system.
-
B.
registrationCategory
Indicates the classification or type under which an entity is formally registered within a system or registry.
-
C.
canonicalCategory
Indicates that an entity is assigned to its primary or standard category within a classification system.
-
D.
generalCategory
Indicates that one entity is classified as a broad or overarching category to which the other entity belongs.
-
E.
category
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
- 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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a56c9f0819094dc87fe55a8823e |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:03 p.m.