Triple
T18724504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Language Models are Few-Shot Learners |
E457860
|
entity |
| Predicate | taskTypesEvaluated |
P133326
|
FINISHED |
| Object | question answering |
—
|
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: question answering | Statement: [Language Models are Few-Shot Learners, taskTypesEvaluated, question answering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taskTypesEvaluated Context triple: [Language Models are Few-Shot Learners, taskTypesEvaluated, question answering]
-
A.
taskType
Indicates the specific category or kind of task an action or assignment belongs to within a broader set of tasks.
-
B.
hasTaskType
Indicates that an entity is associated with or classified under a specific type or category of task.
-
C.
eligibleProjectType
Indicates that a project belongs to a category or type that qualifies it for a specific program, process, or benefit.
-
D.
definesTasksOf
Indicates that one entity specifies or establishes the tasks, duties, or responsibilities assigned to another entity.
-
E.
hasSignificantWorkType
Indicates that an entity is associated with a primary or notably important type or category of work.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d72d2c4819080b0d31860976b5e |
completed | April 20, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49a9bcc0c81908df3e513fd6762ff |
completed | April 19, 2026, 9:04 a.m. |
Created at: April 10, 2026, 11:50 a.m.