Triple
T36489557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ENAS |
E899017
|
entity |
| Predicate | searchesOver |
P186028
|
FINISHED |
| Object | neural network architectures |
—
|
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: neural network architectures | Statement: [ENAS, searchesOver, neural network architectures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: searchesOver Context triple: [ENAS, searchesOver, neural network architectures]
-
A.
searchesVia
Indicates that an entity performs a search by means of, or using, a specified tool, method, or channel.
-
B.
searchingFor
Indicates that one entity is actively seeking, looking for, or attempting to locate another entity.
-
C.
searchesLedTo
Indicates that one or more search actions resulted in, or directly produced, a particular outcome or item.
-
D.
soughtFor
Indicates that one entity is being searched for, pursued, or wanted by another, often for a specific purpose or reason.
-
E.
searchesConductedBy
Indicates that one entity performs or carries out search actions on behalf of or involving another entity.
- F. None of above. chosen
Provenance (4 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_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:10 p.m.