Triple
T315231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iDiscover |
E7690
|
entity |
| Predicate | searchMode |
P5072
|
FINISHED |
| Object | simple 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: simple search | Statement: [iDiscover, searchMode, simple search]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: searchMode Context triple: [iDiscover, searchMode, simple search]
-
A.
searchesSignalType
Indicates that an entity actively looks for or queries a specific type or category of signal.
-
B.
mode
chosen
Indicates the manner, method, or way in which an action, process, or interaction is carried out or occurs.
-
C.
finds
Indicates that one entity discovers, locates, or comes upon another entity, often as the result of a search or encounter.
-
D.
discoveryMethod
Indicates the process, technique, or approach by which something was found, detected, or identified.
-
E.
searchesRegion
Indicates that an entity performs a search operation within, or targeting, a specified geographic or administrative region.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea62f830819089e94b3aa3e4e187 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e9428098819089d5950cd2c96dc4 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.