Triple
T3520382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VGG |
E74406
|
entity |
| Predicate | isBaselineFor |
P2421
|
FINISHED |
| Object | many computer vision benchmarks |
—
|
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: many computer vision benchmarks | Statement: [VGG, isBaselineFor, many computer vision benchmarks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBaselineFor Context triple: [VGG, isBaselineFor, many computer vision benchmarks]
-
A.
isBaseFor
chosen
Indicates that one entity serves as the foundational support, starting point, or underlying basis upon which another entity is built, developed, or depends.
-
B.
isBasedOn
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
-
C.
isMajorBaseIn
Indicates that a location serves as a primary or central base of operations within a specified area or organization.
-
D.
baselineType
Indicates the type or category of a baseline used as a reference point for comparison or evaluation.
-
E.
areBasedOn
Indicates that one entity is founded, derived, or developed from the principles, content, or structure of another entity.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc4af70c8190a7471f28e1efd7fd |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae10689c8190b7dc6d7daa8295b6 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.