Triple
T14785132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Award for Outstanding Short-Form Program |
E347499
|
entity |
| Predicate | contentLengthCategory |
P116096
|
FINISHED |
| Object | short-form |
—
|
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: short-form | Statement: [Award for Outstanding Short-Form Program, contentLengthCategory, short-form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentLengthCategory Context triple: [Award for Outstanding Short-Form Program, contentLengthCategory, short-form]
-
A.
mainContentType
Indicates the primary type or category of content associated with an entity or resource.
-
B.
contentAccess
Indicates that one entity is permitted to retrieve, view, or otherwise use the content provided or controlled by another entity.
-
C.
textContent
Indicates that one entity is the textual content or written material contained within another entity.
-
D.
length
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
E.
contentUsage
Indicates how a piece of content is intended to be used, accessed, or consumed within a given context or system.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deca9f1c9c8190a8b28ba0ddd3e2e3 |
completed | April 14, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de90c5e3a08190868680b081308c1d |
completed | April 14, 2026, 7:08 p.m. |
Created at: April 10, 2026, 1:31 a.m.