Triple
T18016110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VOCSegmentation |
E431001
|
entity |
| Predicate | canDownload |
P79779
|
FINISHED |
| Object | PASCAL VOC data when download=True |
—
|
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: PASCAL VOC data when download=True | Statement: [VOCSegmentation, canDownload, PASCAL VOC data when download=True]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canDownload Context triple: [VOCSegmentation, canDownload, PASCAL VOC data when download=True]
-
A.
downloadFrom
Indicates that a file, data, or resource is transferred and obtained from a specified source or provider.
-
B.
supportsDigitalDownloads
chosen
Indicates that one entity enables or allows the other entity to provide or access digital file downloads.
-
C.
canRetrieve
Indicates that one entity has the ability or permission to retrieve or fetch another entity or resource.
-
D.
canRead
Indicates that one entity has the ability or permission to read or access the content of another entity.
-
E.
canBring
Indicates that one entity has the ability or permission to bring another entity or item to a particular place or context.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b523f588819097389e067dda7f23 |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.