Triple
T849008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GPT-2 |
E18339
|
entity |
| Predicate | evaluationSetting |
P750
|
FINISHED |
| Object | zero-shot evaluation on downstream tasks |
—
|
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: zero-shot evaluation on downstream tasks | Statement: [GPT-2, evaluationSetting, zero-shot evaluation on downstream tasks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaluationSetting Context triple: [GPT-2, evaluationSetting, zero-shot evaluation on downstream tasks]
-
A.
evaluationBasis
Indicates the criteria, standards, or reference framework used to judge, assess, or measure something in an evaluation process.
-
B.
assessmentMethod
chosen
Indicates the method or procedure used to evaluate, measure, or judge something.
-
C.
evaluationCycle
Indicates the recurring period or sequence in which evaluations or assessments are conducted and reviewed.
-
D.
evaluationDataset
Indicates that a dataset is used as a benchmark or test set for evaluating the performance or quality of a system, model, or method.
-
E.
resultDetermination
Indicates the process or criteria by which an outcome, decision, or result is established or concluded from given inputs or conditions.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac1fac3481909cba7070ce31a9b3 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa807adc8190ad808a573cf8e923 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.