Triple
T36489414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASNet |
E899014
|
entity |
| Predicate | transferredToDataset |
P57570
|
FINISHED |
| Object | ImageNet |
—
|
NE NERFINISHED |
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: ImageNet | Statement: [NASNet, transferredToDataset, ImageNet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferredToDataset Context triple: [NASNet, transferredToDataset, ImageNet]
-
A.
transferredWith
Indicates that something was moved or conveyed from one entity to another using a specified medium, method, or accompanying item.
-
B.
transferredUnder
Indicates that something is moved, conveyed, or reassigned from one party, context, or control to another under specified terms or conditions.
-
C.
seeTransferredFrom
Indicates that something is observed or recorded as having been moved or conveyed from a specific source entity to another context or location.
-
D.
transferDestination
chosen
Indicates the entity that serves as the receiving end or target location of a transfer from another entity.
-
E.
transferredRegion
Indicates that control, ownership, or responsibility for a geographic or administrative region has been moved from one entity to another.
- 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_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:10 p.m.