Triple
T36489473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AmoebaNet |
E899015
|
entity |
| Predicate | searchAlgorithm |
P23048
|
FINISHED |
| Object | evolutionary neural architecture search |
—
|
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: evolutionary neural architecture search | Statement: [AmoebaNet, searchAlgorithm, evolutionary neural architecture search]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: searchAlgorithm Context triple: [AmoebaNet, searchAlgorithm, evolutionary neural architecture search]
-
A.
searchSpace
Indicates that an entity explores or examines a defined domain or range of possible options, configurations, or solutions.
-
B.
searchFeature
Indicates that an entity provides or supports functionality for searching or querying information or items.
-
C.
searchingFor
Indicates that one entity is actively seeking, looking for, or attempting to locate another entity.
-
D.
searchesVia
chosen
Indicates that an entity performs a search by means of, or using, a specified tool, method, or channel.
-
E.
relatedAlgorithm
Indicates that one algorithm has a meaningful connection or association with another algorithm, such as similarity, dependency, or complementary function.
- 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_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.