Triple
T30338122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deep contextualized word representations |
E771674
|
entity |
| Predicate | taskCategory |
P87
|
FINISHED |
| Object | language understanding |
—
|
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: language understanding | Statement: [Deep contextualized word representations, taskCategory, language understanding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taskCategory Context triple: [Deep contextualized word representations, taskCategory, language understanding]
-
A.
taskType
Indicates the specific category or kind of task an action or assignment belongs to within a broader set of tasks.
-
B.
calendarCategory
Indicates the classification or grouping assigned to calendar entries based on their type, purpose, or context.
-
C.
categoryForPlanning
Indicates that something is assigned to a specific category used for organizing or structuring planning activities or processes.
-
D.
category
chosen
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
E.
userTask
Indicates that a specific task is assigned to, owned by, or performed by a particular user.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f681cf69588190b1a6373ddf29dd6a |
completed | May 2, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:54 p.m.