Triple
T36491748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omniglot |
E899066
|
entity |
| Predicate | taskSupported |
P55918
|
FINISHED |
| Object | one-shot classification |
—
|
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: one-shot classification | Statement: [Omniglot, taskSupported, one-shot classification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taskSupported Context triple: [Omniglot, taskSupported, one-shot classification]
-
A.
canTask
Indicates that an entity has the ability or permission to perform a specified task.
-
B.
canBeTaskOrganizedWith
Indicates that one entity can be grouped, scheduled, or managed together with another as part of the same task or workflow.
-
C.
userTask
Indicates that a specific task is assigned to, owned by, or performed by a particular user.
-
D.
taskType
chosen
Indicates the specific category or kind of task an action or assignment belongs to within a broader set of tasks.
-
E.
theorySupports
Indicates that one theory provides justification, evidence, or logical backing for another claim, theory, or proposition.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.