Triple
T36491787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | miniImageNet |
E899067
|
entity |
| Predicate | commonlyUsedWithShotCounts |
P4791
|
FINISHED |
| Object | 1-shot |
—
|
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: 1-shot | Statement: [miniImageNet, commonlyUsedWithShotCounts, 1-shot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyUsedWithShotCounts Context triple: [miniImageNet, commonlyUsedWithShotCounts, 1-shot]
-
A.
frequentlyUsedBy
Indicates that something is regularly or commonly utilized by a particular entity.
-
B.
isOftenRecordedWith
Indicates that one entity is frequently documented, captured, or logged at the same time as another entity.
-
C.
beatUsedIn
Indicates that a particular beat or rhythmic pattern is employed within a specific musical piece, section, or context.
-
D.
isFamouslyUsedIn
Indicates that something is widely recognized or well-known for being used in a particular context, work, or situation.
-
E.
usedWith
chosen
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
- 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_69ff14d596e88190be5263b7f96a96cd |
completed | May 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69ff13f0208081909369aeb3b77a6b1f |
completed | May 9, 2026, 11:01 a.m. |
Created at: May 3, 2026, 4:10 p.m.